[FIXED B1147.25] Out of memory exception

[thewood1]

This is ground hog day.

[morphin]

ORIGINAL: ultradave

I downloaded both your saves. Can you provide a little more detail?

1. You mention random course changes, and arbitrary sub depth changes and course changes. Can you provide more detail, specifically what unit should I monitor and when does the change happen following loading your save?

2. Crashes and out of memory error. Does the out of memory error cause a crash? Also, what specifically were you doing when the game crashed or caused an out of memory error?
( I have loaded both, run forward and changed simulation speed from 1x to max a number of times. So far it is behaving well for me. My computer is not as high spec as yours. In fact, it's a MacBook Pro, running W10 in Parallels Desktop, which runs CMO quite well. I've never had CMO or C:MANO for that matter, crash on me. Not once.)

3. What revision of CMO are you running?

4. Do you have these issues with any other scenarios? For example, have you set up a simple test scenario for the changing courses/depth issue?

I'd be happy to poke around more if I have a more specific idea of what to watch for.

Dave

1. about 5 Enemy subs (but also own subs) are suddenly surfaced (like AndrewJ has also remarked in other scenario (https://www.matrixgames.com/forums/tm.a ... 65&mpage=2). I have seen this in a couple of other scenarios too (larger ones).
Also the sudden course changes i have also had in other scenarios you should see just after loading (without starting the scenario). Here all the courses that are doted were set from me before (you should see at least a few courses that are dotted in on save files). That suddenly happens.

2. The game last time crashes not while playing, but next day when i come back to the computer (Red Cross displayed through the CMO Window). I often let the computer running 24h. A few month ago i had this regularly (after a few houres come back playing), but now it is very rare that this happens. . But for me this is not the most urgent thing. (I could close CMO and start CMO again on next day to prevent this). What i do maybe more than others is loading a previous savegame often (i do no use autosave. On bigger scenarios they still fail regularly). So some thing to check is if some (static) variables are not cleanly disposed and second thing would be which background processes are still running when game is paused and could make these error messages.
3. Latest 1147.18

4. https://www.matrixgames.com/forums/tm.asp?m=4933666 and https://www.matrixgames.com/forums/tm.a ... age=4&key=


Andy

[Zanthra]

ORIGINAL: morphin

Hi Zanthra

Thank's for helping.

Month ago i did already an analysis about memory. I even recorded performance counters. There is no limitation on my system (32GB Memory and 8GB Pagefile).
CMO is only using small part of the memory (also if it crashes is only using about 2GB when it crashes. No raising of memory usage at the time it crashed). It only crashes rare now so new version fixed something.
I'm not the only one, but yes this behaviour is rare.

One thing are the limitations of a 32 BIT Programm (see https://www.matrixgames.com/forums/tm.a ... age=1&key=). I hope they are considering to go to 64 BIT

But good thing is that the application is logging this error and with the error descriptions and finding the locations in the code and with a little bit of research the developer should resolve this

Thank's

8GB of page file for 32GB of RAM is considered small. Windows by default allocates 36GB of page file on my system with 24GB of RAM. While I don't actually think it's likely in this case, I have seen problems like this in the past even when physical memory usage was low (to be fair at the time total system memory was much lower), and I think setting a larger page file is definitely worth the try. 1.5 times RAM is the often recommended page file size, for 48GB.

[ultradave]

Andy,

Well, I've had no luck reproducing any of the problems you are seeing. I loaded and ran your saves and I see the Groton diving from the surface, but when I load the scenario from new, all of my submarines act normally. I changed speeds, depths, courses multiple times and and let the sim run for hours and kept checking each subs. All normal. I made multiple saves and reloaded from the saved games, with no crashes and no changes to behavior. The same results with the Pacific Fury scenario (although I didn't run that one as long). All my subs acted as they should. No unwanted surfacing noted, and no magically appearing enemy subs.

I also for comparison ran a few other submarine scenarios (they are small ones so if this is really a big scenario issue then this may not matter). Scenarios from Silent Service, and the Push scenario from Chains of War all behave normally. I also started up X-Ray Station from Northern Fury and that one behaved well as well. I don't think I've started that one in CMO before , just C:MANO.

For reference, I run on a MacBook Pro, with 8GB RAM and Intel Iris Plus Graphics 655 (1536 MB), running W10 in Parallels Desktop. I let Parallels use maximum resources from the Mac because when I'm running it I'm not doing anything in parallel(haha) on the Mac.

So, sorry to not be able to recreate your experience and be able to notice something, but maybe this is helpful too. I was hoping to come across some sequence that led to an issue.

Dave

[WSBot]

0014477

[Crossing the T]

I can confirm the memory issues. When loading a complex scenario, CMO takes about 800MB of memory. Once I run it, the memory usage rises constantly to above 2GB, and around 2.5GB the program crashes. Sometimes I still get an error message (out of memory exception, autosave unsuccessful). There seems to be a memory leak. Or perhaps perform a garbage collection once you come across an out of memory exception?

And guys, do port the game to 64bits, will you? I've got a 32GB machine, and I expect any halfway recent, beyond-trivial game to use memory above 4GB. It's there to be used!

Regards,
Stefan

[Dimitris]

ORIGINAL: Crossing the T
I can confirm the memory issues. When loading a complex scenario, CMO takes about 800MB of memory. Once I run it, the memory usage rises constantly to above 2GB, and around 2.5GB the program crashes. Sometimes I still get an error message (out of memory exception, autosave unsuccessful). There seems to be a memory leak. Or perhaps perform a garbage collection once you come across an out of memory exception?

Since from your description you seem to be encountering an OOM issue with great consistency, can you please lay out the precise steps (incl. specific scenario) to reproduce it? Thanks.

[Crossing the T]

ORIGINAL: Dimitris
Since from your description you seem to be encountering an OOM issue with great consistency, can you please lay out the precise steps (incl. specific scenario) to reproduce it? Thanks.

Sure.
Can't post game version, because the forum software thinks it's a phone number [&:]
I start the launcher via Steam.
The launcher has to be started as admin, otherwise it won't start (compatibility settings in Launcher.exe)
Starting the "Command.exe" directly from the game directory results in a license issue for the "Kashmir Fire" campaign (appears as unlicensend).
From the "Kashmir Fire" campaign, I start the "escalation" scenario or load a saved game from that scenario.
Watching the game's memory usage in Task Manager, I see it starting with around 800 MB memory usage. Within the next 30 minutes or so, the usage steadily climbs up, until at around 2.5G, the game crashes. The GUI is gone, but the game process is still in memory. Steam cannot stop the game process. After killing Command.exe manually, only a Steam restart allows starting the game anew.

Hope this helps!

Stefan

[Dimitris]

ORIGINAL: Crossing the T
Sure.
Can't post game version, because the forum software thinks it's a phone number [&:]
I start the launcher via Steam.
The launcher has to be started as admin, otherwise it won't start (compatibility settings in Launcher.exe)
Starting the "Command.exe" directly from the game directory results in a license issue for the "Kashmir Fire" campaign (appears as unlicensend).
From the "Kashmir Fire" campaign, I start the "escalation" scenario or load a saved game from that scenario.
Watching the game's memory usage in Task Manager, I see it starting with around 800 MB memory usage. Within the next 30 minutes or so, the usage steadily climbs up, until at around 2.5G, the game crashes. The GUI is gone, but the game process is still in memory. Steam cannot stop the game process. After killing Command.exe manually, only a Steam restart allows starting the game anew.

Hope this helps!

Thanks. We had a look at this.

This is a case-specific RAM-exhaustion issue (not a leak per se, but more a case of "not giving the GC a chance to do its job for a while"), which has been fixed by the B1147.25 update released a few days ago and available here.

Please give it a go and let us know.

If there is any other scenario in which you have observed a similar issue, please try it with this update and let us know too.

Thanks!

[Crossing the T]

ORIGINAL: Dimitris

This is a case-specific RAM-exhaustion issue (not a leak per se, but more a case of "not giving the GC a chance to do its job for a while"), which has been fixed by the xxxx update released a few days ago and available
Please give it a go and let us know.

That has done the trick! Now memor yusage stays around 1GB, and even when I stress the game, it doesn't go above 1.5.

Thanks!

Stefan