"Currently compiling. Stop compilations and exit?" - replying Yes causes a hang.

[pabristow]

Sometimes I have forgotten to close the 'run' window (In mitigation, I plead that it is hidden behind the main window) before closing CB down.

After some hangs, and losing workspace info, I have realised that asnwering 'yes' to this results in the 'hang'.  The pointer turns into an hourglass and the screen goes greyed, and if eventually I press the exit cross, it bombs out complaining to Microsoft :-(

Answering no, and closing the 'Run' window properly as one should, and then shutdown works OK.

My recollection that negligent behaviour like this was handled OK before.

Know feature?

CB 20.03 on Windows 10, all compilers?

[oBFusCATed]

Can you describe the exact steps to reproduce the problem?

[pabristow]

Start CB (on windows 10)

Create a new project, hello world perhaps, and run it, but

Don't close the run window!

Then
Close CB and you get a CB Pop box asking if you want to stop compiling.

Answer Yes

CB window is now greyed out and hangs.
If you try to close by clicking X, it says codeblock IDE has stopped responding.

Choosing 'Close the program' option send a report to Microsoft :-(

I suspect that this problem is Windows-specific.

Workaround is simpl - don't answer Yes!"  Answer "No" and close the run window properly first (when prompts you to save workspace etc). 

But CB should not do this (it didn't before I believe).

[oBFusCATed]

I suspect that this problem is Windows-specific.

No, it is not. Would it be possible to log it on our tickets page on sf.net?

[pabristow]

https://sourceforge.net/p/codeblocks/tickets/976/

thanks for confirmation :-)