VS 2008 console window stays up

[Rick]

Does anyone using VS 2008 have an issue with the console window sometimes staying open even when you have exited debugging? Every so many runs the console window stays up for me.

[MrIslomaniac]

That sometimes happens to me, but i disabled the console for the release version =)

http://www.leadwerks.com/wiki/index.php?title=Setting_Up_Visual_Studio_2008_C%2B%2B_Express at the bottom

[Mumbles]

I find the console only stays up if I run the project without debugging (CTRL F5), in either debug or release configs (and I only ever use release)

[Rick]

and I only ever use release

 

Don't you ever step through your code when debugging things?

 

 

That sometimes happens to me, but i disabled the console for the release version

Yeah me too, but I do a ton of debugging before release, so it's kind of annoying to have these console windows open that I can't seem to close.

[Rick]

OK, seriously has anyone found a way to close these prompt windows? I have like 7 of them open but I can't close them.

[macklebee]

reboot?

[Rick]

Sadly that is the only way I was able to get them to go away. What really sucks is it seems I have to hard power it off. Start->Reboot doesn't seem to work. Not sure if they are still running and XP can't pull the rug out.

[VicToMeyeZR]

only time I had that happen, I was able to tell VS to stop the debug, and they go away.

[Canardia]

You can close the windows when you press Shift-F5 in VC2008. But it only works when your program doesn't crash, so don't make mistakes in your code.

[Rick]

I'm not making mistakes, I just don't let the program exit fully. When I run I'm usually testing a specific spot in the middle of the code. Once I see it works I just press the stop button. But sometimes the windows go away and sometimes they don't.

[Mumbles]

Oh, I didn't realise you meant staying open, as in: "Can't be closed". What I get, program closes the console then says "Press any key to continue . . . . ." Press any key, and it closes.

 

Since I can't replicate the situation, I can only guess, and assume that ending the process cmd.exe doesn't have any effect?

[Canardia]

It's not cmd.exe which runs it, but the actual exe name which VS2008 creates.

Howeever, when that happens, the whole exe is not even visible in the process list of Task Manager!

And when you try to close the window, there never comes even that "Program is not responding, press End to end it." dialog.

And when you try to log out or to restart Windows, Windows just hangs.

 

The only semi-safe way to close the hanging windows is to close all programs, and then kill all remaining processes from Task Manager, then wait a minute or two until there is for sure no harddisk action anymore (make sure to pull the network cable out, to prevent that some programs start to alter files on your harddisk when they create internet cache files), and hit the reset key.

 

That way you don't get a forced Check Disk from XP, since all files were closed when the hard reset happened.

Hard reset is still "softer" than hard power-off (which is also softer than "powercable out"), but it depends on your hardware if they are softer. Anyway, it can't harm to use hard reset instead of hard power-off, since it can't be harder in any case.

 

So, instead of going through this process several times a day, I think Josh should fix it

It didn't happen before LE 2.31.

[Rick]

I agree. For now I just turned off the console and I'll just look at the engine.log. I had like 10 console windows open. Very annoying.