[FIXED B527] Command32.exe does not clear from memory after closing

[Kitchens Sink]

Build 521 on a Windows 7 machine. After closing Command, I run computer Task Manager and have to manually close Command EXE process (anywhere from 500 to 800 mb memory use). This happens about 70% of the time, usually after running a larger scenario for an extended period. I found this out after computer started running slow and I found that I had 3 instances of Command32.exe running after closing.

Possibly this is something with my computer, but seems strange as nothing else seems to hang around in memory after closing.

[Dide]

Me too!

[thewood1]

I have seen this infrequently. It seems to happen in only a couple instances: when I play a long session over multiple hours and when my laptop sleeps while a session is running and then I shut it down on awakening. I have seen it maybe once a month, that I noticed.

[Windom Earle]

Chances are at almost 100% for me - because I play complex scenarios mostly. No matter how long I play - then I quit CMANO, 50% of CPU power is still occupied by it (dual-core processor) indefinitely. Windows 7 32 bit, 2 GB RAM total.

[mikmykWS]

Thanks guys,

We know this issue exists although it doesn't happen to everybody everytime and TheWood1 does kind of sum of what we know about users that experience it.

A few question to see if we can learn more:

How are you exiting command? Red x or menu?
Can you confirm your OS version? This seems to happen with Win 7 more often than not.
Memory?

Thanks!

Mike

[Kitchens Sink]

I exit Command with File/Exit, not the red X. I am using Windows 7 and have 8 GB RAM on a newer ASUS computer. It only seems to happen on larger scenarios for me, but it does not matter whether I am playing for 5 mins or 5 hrs.

[ryszardsh]

Happens infrequently to me, W8.1. I do not always exit the same, sometimes the red X, sometimes the menu, sometimes a crash and force not using alt-ctrl-del but just letting Windows run through its trouble shooter. I do not see any real difference in when I get the run-on .exe after shutdown by type of shutdown but it does seem correlated to running a large scenario.

RAS

[Dide]

Hi, i'm using Windows 7 64 bit, with 8 gb ram, and I exit Command with File/Exit.

[Dannyp19]

I've had this problem on the larger scen.'s after a crash/lock up. I haven't had this happen during a normal shutdown of the program since a few builds ago. Come to think of it I haven't seen this at all since the latest build. But due to work my CMANO time has been very limited the last few months[:(]

Win. 7 64 bit. 16 GB RAM

[Dimitris]

This has been resolved in Build 527.