Memory Leak

[klem]

I am wondering about the nature of this memory leak. In a utility I have called Membooster, which optimises memory to recover isolated unused memory, I see two things (also it can be seen in Task Manager). On the one hand the memory usage creeps up with time but I also see a quick 'ramp up' of memory usage over a minute or two, about a 40 degree slope, before it drops vertically back to what it was. I can't find a consistent cause for this.

Is anyone else seeing this 'ramping'?
Does anyone know if it is the game or some other service?

I also tried Gamebooster to close down unecessary services but it still happens.

[FG28_Kodiak]

.Net has a Garbage Collector, this tries to free Memory if possible. So what you "see" is the Gabage Collector in Action, i think.

[SEE]

On my system, the frequency of Launcher crashes is proportional to my video settings. I have reverted back back to Med settings for everything except Model/Damage Detail to High, Trees/Shadows/SSAO/AA Off and Vsync disabled and Triple Buffering set to off.

I also try to avoid excessive use of the zoom function when particle rendering is taking place which seems tied into the 'effects' setting.

With the above I can be in MP for a lot longer without the dreaded Launcher crash and my fps is much higher even over the dreaded low altitude hot spots.

After fitting a 2gb GFX card, I cranked the setting to High and started getting LE crashes more frequently.

[JG52Krupi]

Originally Posted by SEE

On my system, the frequency of Launcher crashes is proportional to my video settings. I have reverted back back to Med settings for everything except Model/Damage Detail to High, Trees/Shadows/SSAO/AA Off and Vsync disabled and Triple Buffering set to off.

I also try to avoid excessive use of the zoom function when particle rendering is taking place which seems tied into the 'effects' setting.

With the above I can be in MP for a lot longer without the dreaded Launcher crash and my fps is much higher even over the dreaded low altitude hot spots.

After fitting a 2gb GFX card, I cranked the setting to High and started getting LE crashes more frequently.

+1 apart from the odd random crash by having my setting reduced to medium I can fly for a lot longer before CTD

[icarus]

Originally Posted by SEE

On my system, the frequency of Launcher crashes is proportional to my video settings. I have reverted back back to Med settings for everything except Model/Damage Detail to High, Trees/Shadows/SSAO/AA Off and Vsync disabled and Triple Buffering set to off.

I also try to avoid excessive use of the zoom function when particle rendering is taking place which seems tied into the 'effects' setting.

With the above I can be in MP for a lot longer without the dreaded Launcher crash and my fps is much higher even over the dreaded low altitude hot spots.

After fitting a 2gb GFX card, I cranked the setting to High and started getting LE crashes more frequently.

+1

After fitting with a 3 Gb vid card I saw the memory usage creep up to over 2.5 GB!

[priller26]

I must be incredibly lucky, to date I have not had a single CTD, with over 33 hours flown.

[JG52Krupi]

Originally Posted by priller26

I must be incredibly lucky, to date I have not had a single CTD, with over 33 hours flown.

Online? The crash is only a multiplayer bug!

[ZaltysZ]

Originally Posted by FG28_Kodiak

.Net has a Garbage Collector, this tries to free Memory if possible. So what you "see" is the Gabage Collector in Action, i think.

I think so too. People should not put too much attention to spikes of memory usage, because garbage collector does not free the memory the moment it becomes unused, it does free it when it thinks it is good time to do that.