Console Window not closeable, and no process attached

MasterD · Post by **MasterD** » Mon Mar 01, 2010 8:58 pm

I'm currently not sure, if this irrlicht related at all, but I'm experiencing strange problems with closing my windows application.

The problem is, that sometimes the Irrlicht 3D window is closed correctly, but the console window still remains. Even uglier, there is no process attached to that window. So I can't terminate it with the task manager or some tool like sysinternals process explorer. Even windows itself is not able to terminate it and can't shut down anymore.... So currently my laptop is doomed for a hard reset or a lifelong uptime .... Since its windows, it will be the first

I'm tracking down the issue, but I have no clue, currently. I could reproduce it when closing the debugging while a assertion is triggered (which is implemented as asm { int 3 }).

Anyone experienced similar issues before? Maybe this is not irrlicht related at all? Is anyone using similar assertions, what happens if you quit the debugger while it is triggered?

zillion42 · Post by **zillion42** » Mon Mar 01, 2010 9:16 pm

dito / Ibid !
see:
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=37314

windows refusing to shut down is what bothers me most. I suspect a windows update in fact, but who knows...

hybrid · Post by **hybrid** » Tue Mar 02, 2010 12:46 am

I also have these problems when stopping on usual breakpoints. About one or two weeks now. Very annoying, as I tend to shut down my computer only very seldomly.

MasterD · Post by **MasterD** » Tue Mar 02, 2010 10:44 am

So I suspect a Windows Update as well, since I'm still using irr 1.6 and it only occured recently. I'm using XP, what are you using?

Have you ever noticed this without a debugger attached?

zillion42 · Post by **zillion42** » Tue Mar 02, 2010 5:04 pm

I also shut down very seldomly, thats why I have 28 minimized console windows open at the time of writing...

However I you stop at the breakpoint, step and debug to your hearts desire, then remove the breakpoint and press the play button again ("start debugging") and wait for irrlicht to start looping it is then safe to stop debugging for the console window will close as it should as long as irrlicht was really running.
If it crashes though, the console remains open after the app has stoppped.

EDIT: XP aswell here and No, it only happens in debug for me, never in release.
EDIT2:
http://boardreader.com/thread/VS_2008_d ... 9e3ca.html
EDIT3:

The Problem is with the KB978037
once removed everything return to normal!

mdeininger · Post by **mdeininger** » Tue Mar 02, 2010 5:30 pm

not sure if this is gonna help in any way, but i've seen this happen a lot with borland and console applications as well. occasionally when i try to stop/kill the process in borland, poop goes wonkers all over the place.

seems to only be related to console windows as well. (using windows xp here)

zillion42 · Post by **zillion42** » Wed Mar 03, 2010 12:40 am

confirmed working for me, removing KB978037 fixed the issue.
To do that, windows style

go the control panel -> software,
check "show updates",
sort by date and find KB978037 close to the end of the list,
remove it,
ignore the message about other applications potentially not working anymore,
reboot.

MasterD · Post by **MasterD** » Wed Mar 03, 2010 9:14 am

So it is definetly a Windows update and not irrlicht bound, thanks for the link, zillion42.

But, since I wanted to put up a release soon and don't want to raise the anger of the users:
Did this ever happen to one of you with a release build and no debugger attached?

B@z · Post by **B@z** » Wed Mar 03, 2010 9:22 pm

if u compile the release w/o console, then this problem wont happen right?

zillion42 · Post by **zillion42** » Thu Mar 04, 2010 2:53 pm

what a relief... and no, not in release.

EDIT: XP aswell here and No, it only happens in debug for me, never in release.

Scarabol · Post by **Scarabol** » Sun Apr 25, 2010 10:44 am

Hi,

i got the same problem.
But, in my Software list it says "Update removed". What to do now?
Removed by SP3 maybe?

MfG
Scarabol

MasterD · Post by **MasterD** » Tue Apr 27, 2010 8:42 pm

If you don't rely on some debug output from the console, you can remove it with something like the following, instead of your current main (just replace it)

Code: Select all

int __stdcall WinMain(HINSTANCE, HINSTANCE, LPSTR, int)

I think, that this bug is not on MS' high priority list, so I removed the console window for now, although it continued some useful information.

Scarabol · Post by **Scarabol** » Wed Apr 28, 2010 7:15 am

Hi,

it was SP3 i removed it an voila i could remove the update.

Damn service packs always problems

(

MfG
Scarabol

Murloc992 · Post by **Murloc992** » Sat May 01, 2010 2:49 pm

*ressurection of an old post*

I am having this issue too and what's worst, can't remove the update nor SP3

Any advices?