how to read log, oom error

[ryan884]

428940 **** WARNING! Free memory is very low!

438956 **** WARNING! Free memory is very low!

448987 **** WARNING! Free memory is very low!

459002 **** WARNING! Free memory is very low!

469048 **** WARNING! Free memory is very low!

479095 **** WARNING! Free memory is very low!

489157 **** WARNING! Free memory is very low!

499188 **** WARNING! Free memory is very low!

509203 **** WARNING! Free memory is very low!

519249 **** WARNING! Free memory is very low!

529296 **** WARNING! Free memory is very low!

539342 **** WARNING! Free memory is very low!

549420 **** WARNING! Free memory is very low!

559466 **** WARNING! Free memory is very low!

569497 **** WARNING! Free memory is very low!

579513 **** WARNING! Free memory is very low!

589575 **** WARNING! Free memory is very low!

599605 **** WARNING! Free memory is very low!

609652 **** WARNING! Free memory is very low!

619730 **** WARNING! Free memory is very low!

629776 **** WARNING! Free memory is very low!

639823 **** WARNING! Free memory is very low!

649869 **** WARNING! Free memory is very low!

659900 **** WARNING! Free memory is very low!

669915 **** WARNING! Free memory is very low!

679962 **** WARNING! Free memory is very low!

690008 **** WARNING! Free memory is very low!

700070 **** WARNING! Free memory is very low!

710101 **** WARNING! Free memory is very low!

720116 **** WARNING! Free memory is very low!

730163 **** WARNING! Free memory is very low!

740225 **** WARNING! Free memory is very low!

750287 **** WARNING! Free memory is very low!

760318 **** WARNING! Free memory is very low!

770333 **** WARNING! Free memory is very low!

780364 **** WARNING! Free memory is very low!

790379 **** WARNING! Free memory is very low!

800394 **** WARNING! Free memory is very low!

810456 **** WARNING! Free memory is very low!

820487 **** WARNING! Free memory is very low!

830518 **** WARNING! Free memory is very low!

840549 **** WARNING! Free memory is very low!

850564 **** WARNING! Free memory is very low!

860611 **** WARNING! Free memory is very low!

870642 **** WARNING! Free memory is very low!

880657 **** WARNING! Free memory is very low!

890735 **** WARNING! Free memory is very low!

900750 **** WARNING! Free memory is very low!

910796 **** WARNING! Free memory is very low!

920812 **** WARNING! Free memory is very low!

930827 **** WARNING! Free memory is very low!

940842 **** WARNING! Free memory is very low!

950873 **** WARNING! Free memory is very low!

960888 **** WARNING! Free memory is very low!

970919 **** WARNING! Free memory is very low!

980966 **** WARNING! Free memory is very low!

Im not sure how to read this log, do those numbers mean memory blocks or something. I need to fix this oom error.

[Pete Dowson]

Im not sure how to read this log, do those numbers mean memory blocks or something. I need to fix this oom error.

The numbers on the left are the number of milliseconds sibce FSUIPC started. There's no more information here about your memory. When it is below 300 mb free you'll get this warning. It is re-checked every 10 seconds, as the times show.

Fixing OOMs is by reducing FS sliders or using less detailed, less complex scenery and aircraft.

Regards

Pete

[ryan884]

The numbers on the left are the number of milliseconds sibce FSUIPC started. There's no more information here about your memory. When it is below 300 mb free you'll get this warning. It is re-checked every 10 seconds, as the times show.

Fixing OOMs is by reducing FS sliders or using less detailed, less complex scenery and aircraft.

Regards

Pete

Ok i know you can reduce ooms by reducing sliders but i thought there might be something to diagnose the ooms, but i guess not. Anyway i was flying from jfk to bdl and the first time i was flying around 15 minutes and it oomed. Not suprising but the second time i tried to fly from jfk to bdl with same settings randomly after clicking a panel on the 737ngx everything in the cockpit and the scenery became blurry. I realised i was probably close to oom there but the blurring saved me. After clicking esc then clicking continue flight the bluriness went away but it oomed 5 minutes later anyway. Anyone know why the bluriness happend. Btw my fsuipc doesnt make the ding when its about to oom even though i see it in the log after.

Hopefully all my ooms will be solved when i switch to 64 bit windows.

[Pete Dowson]

Ok i know you can reduce ooms by reducing sliders but i thought there might be something to diagnose the ooms, but i guess not.

No, sorry. It's just the 3Gb memory usable to FS (including its own code etcetera) getting used up and fragmented. Sometimes saving a flight will tidy it up and either free some or at least defragment it so larger contiguous space is available. What is actually using it would be very difficult to determine. you can't tell by just looking at it -- it is just binary data. The only way would be to try to hook into the memory allocation API in Windows and log where the cals come from. And that isn't nice because the actual part responsible could be several layers back, so it needs a stack dump each time to find the originator. All this would slow everything down too much and create many megabytes of data which may not even help in any case.

The only way is by trial and error using a process of elimination. Maybe it's only one specific scenery add-on? Maybe some specific AI? Or weather -- maybe using 4096 clouds is just too much?

If you have a registered install of FSUIPC then you could try enabling the AutoSave. Having a flight regularly saved might help. At least some folks report so.

Regards

Pete