07.02.2008, 01:17
Here is a snippet from the SEOW forum.
BS8th_Bulau wrote:
I entered >GC into chat at 2 minute and 1 minute intervals. Memory total reported as follows:
...
0:13 94.5mb
0:14 94.1mb
A few seconds later, the game locked up.
A tell-tale sign of the stupid memory bug in IL-2. The limit is at 96 MB (even if your PC has 4 GB). Over 90MB, you may already experience strange lagging, pulsed warping, as the underlying JVM is desperately trying to free any garbage memory, anticipating a total congestion coming on.
Normally maps use 25-50, or with heavy object population 60-70MB. But larger and more detailed maps definitely use more memory, event with same number of objects, than small ones.
There is a temporary workaround for 4.08, but I reported this bug to the dev team, so may I kindly ask you to test the same with 4.09 beta patch? The result would be interesting for many of us.
or this:
I've had a chance to do a little testing of this. I've copied our big mission onto the Prokhorovka, Smolensk, and Moscow1 maps. The only editing I did was to make sure all the aircraft takeoff and landing waypoints were at an airbase.
Prokhorovka easily ran for an hour, starting out at 41.5 megs, and never rising higher than 47.2 megs total memory. At one hour, this mission is essentially winding down, and I saw no reason to continue any longer test.
Smolensk also ran for an hour without even working up a sweat, starting at 39.4 megs, and reaching a high of 40.8 megs, finishing the hour at 39.0 megs.
Moscow1 has not been run for the hour duration at this time. I started it, and checked memory use immediately, finding it to be using 40.2 megs. I expect that it would play out similarly to the foregoing two maps, and last the hour without incident.
As per the request from Zoli, I tested the original mission on the Ostfriesland map, using the latest 4.09 beta patch. In two attempts, it seemed to fare even worse than 4.08, starting at 73 megs, and lasting only 10 minutes before locking up, using a little over 88 megs at that point.
BS8th_Bulau wrote:
I entered >GC into chat at 2 minute and 1 minute intervals. Memory total reported as follows:
...
0:13 94.5mb
0:14 94.1mb
A few seconds later, the game locked up.
A tell-tale sign of the stupid memory bug in IL-2. The limit is at 96 MB (even if your PC has 4 GB). Over 90MB, you may already experience strange lagging, pulsed warping, as the underlying JVM is desperately trying to free any garbage memory, anticipating a total congestion coming on.
Normally maps use 25-50, or with heavy object population 60-70MB. But larger and more detailed maps definitely use more memory, event with same number of objects, than small ones.
There is a temporary workaround for 4.08, but I reported this bug to the dev team, so may I kindly ask you to test the same with 4.09 beta patch? The result would be interesting for many of us.
or this:
I've had a chance to do a little testing of this. I've copied our big mission onto the Prokhorovka, Smolensk, and Moscow1 maps. The only editing I did was to make sure all the aircraft takeoff and landing waypoints were at an airbase.
Prokhorovka easily ran for an hour, starting out at 41.5 megs, and never rising higher than 47.2 megs total memory. At one hour, this mission is essentially winding down, and I saw no reason to continue any longer test.
Smolensk also ran for an hour without even working up a sweat, starting at 39.4 megs, and reaching a high of 40.8 megs, finishing the hour at 39.0 megs.
Moscow1 has not been run for the hour duration at this time. I started it, and checked memory use immediately, finding it to be using 40.2 megs. I expect that it would play out similarly to the foregoing two maps, and last the hour without incident.
As per the request from Zoli, I tested the original mission on the Ostfriesland map, using the latest 4.09 beta patch. In two attempts, it seemed to fare even worse than 4.08, starting at 73 megs, and lasting only 10 minutes before locking up, using a little over 88 megs at that point.