Trying to remove some processes to reduce OOM issues.

 

NVidia Driver Helper Service

NVidia User Experience Driver Component.

igfxpers.exe - persistence module (also NVidia related I believe)

 

Are these ok to shutdown? I think the help is ok to shutdown but not sure about the user experience. thanks,

OOM errors occur when a process, e.g. FSX, uses up all of its heap's address space, which unfortunately has nothing to do with any other process running on your computer. Short answer: stopping other programs/services will not solve FSX OOM errors. More on the long answer: all programs use a portion of its address space, referred to as a heap, to dynamically allocate chunks of memory which the program requests as needed as it runs. Unfortunate a 32 bit program, such as FSX, has a very finite size to its heap which when exhausted by "too many" allocated memory chunks causes the program grief, in which case for FSX results in a fatal OOM. BTW a 64 bit program's heap is amazing huge in comparision, say at least 1000x bigger (provided you have the RAM and swap space to cover it).

Good info. Turns out by shutting down some processes I got rid of the problem, not quite sure why it worked. I also did the heap adjustment in Windows 7.

Good info. Turns out by shutting down some processes I got rid of the problem, not quite sure why it worked. I also did the heap adjustment in Windows 7.

 

Which "HEAP" did you adjust, and how ??

 

Adjusting the Windows heap, should NOT have made any difference to FSX OOMs.

 

see

http://www.ehow.com/...-windows-7.html

 

On the subject of FSX OOMs, the closing of FSX when there is no available memory to meet a memory request in the FSX code, is actually programmed into FSX. ( so I am told {wink} )

 

Unfortunately, the action is to terminate the FSX process, thus closing down FSX.

 

While it is good practice to expect, and pro-actively deal with these sort of issues (like running out of memory), I suspect that at the time ACES did not really expect this to happen, and just for safety, and good programming practice, programmed the most simple exception solution, namely to have FSX close, if it ran out of memory.

 

In hindsight, with the growth of more complex aircraft and scenery addons, the 32 bit memory limitations of FS are now commonly met, and when this happens, FSX does, as it was programmed to do, and shuts down.

 

However, it only shuts down, because that is what it programmed to do. It could equally well have been programmed with a more forgiving exception processing, to say, recover non critical memory use, and have a system of memory management, that took care of potential OOMs.

 

While a little late, and now difficult to add to FSX (although I suspect Peter Dowson might be able to so in FSUIPC), there might be a good argument for LM to look at this inherited FSX processing of low memory, and alter the P3D code to take less drastic action, than just blindly terminating P3D.

 

 

If a future version of 32 bit P3D NEVER could OOM, that would be a very compelling reason to switch to P3D !!