FS9 crash "out of memory" with 2GB of ram.

[FPEMiller]

Anyone else have this problem?

*Note: This problem happens when using USA-West 38.2m terrian mesh. However, I don't believe this is a problem with the USA 38.2 Terrian, it just compounds an underlying FS problem.

When flying to/from or around KPHX, FS starts using large amounts of memory. FS's usage (both RAM and Virtual Swap memory) slowly keep building until eventually FS crashes with error message "out of memory" . This happans as the memory usages goes just over 1GB of RAM and 1GB of Virtual.

If I disable the USA-West 38.2m terrian, the memory usage peaks out around 650MB, almost double of that of anywhere else (with 38.2 enabled). Again, only around the KPHX area. I have no other scenery addon's running for the KPHX (Arizona) area. If I start at KPHX and fly away from the Arizona area, the memory usage remains high and it doesn't appear to shed the memory load down to what you might see if one's flight originated elsewhere.

I'm thinking it's a texture issue with the default (desert) textures since I don't have this problem any where else (US, Canada) using the 38.2m terrians (including Alaska).

Any thoughts would be appreciated.
System spec's: 2 GB RAM; dual AMD Opteron 248 processors; XP Pro; Swap file currenlty +2GB set to autosize as needed;
Thanks,
MK

[btwallis]

What a frustrating night of flightsimming. I to was having something similar. I was using FS9 yesterday. I loading up and tried out Justin Tyme's 38.2 mesh for Rockies. Everything worked great, flew around a bunch of places. I used FSSE to beef up the north rim of the grand canyon putting a lodge there and vehicles and people. Everything was fine. Shut down went to bed.

Tonight, my goal was to look into beefing up Mexico which is very weak in FS9. I downloaded all sorts of files and installed as usual.

However, I went to start up FS9 the thing kept crashing would not get beyond the splash screen without an "out of memory error" and I have many gigs of space in virtual memory and a gig of RAM etc. I poked around for two hours tonight checking out my scenery.cfg file for corruption. I uninstalled all the scenery I loaded up even thought it was not actually in the library yet. Nothing worked.

I then retraced my steps yesterday and realized "wondered" if the FSSE work I did yesterday had somehow. I went into the LAGO folders and removed the work I did yesterday, including data, sound files.

AND, PRESTO...FS9 "took off" no problem. The issue was related to LAGO FSSE somehow, I have no idea. So, the moral of my story is that sometimes its not what you might first expect it to be.

Right now I would not be a good salesman for LAGO products given the time I wasted and could have been flying.

I suspect this will not be of much value for you but it does point our a "bug" that can occur with the LAGO product and can cause your fs9 to crash.

[PHCO]

Wow, :-eek and I thought I am the only person having this problem. :-lol Well, mine is at least similar. I also get the "Out of memory" message. The strange thing is that it suddenly occured without any reason. I have tried to make some tests and in the moment I can say that it only happens with the FSD Piper Navajo Panther and after I have installed Flight1 USRoads. I am a little bit confused because I am using the Navajo for some time without any problem. Also that this problem could be caused by USRoads is strange because the memory usage with another aircraft-type than the Navajo is normal - so all in all I am a little bit lost. :-roll It didn't happen for some time, so maybe I have by chance solved the problem - I don't know ?! I also have more than enough power - 1GB RAM / 3,2 Ghz.

[alastairmonk]

One thing to check is to make sure that any Landclass scenery folders DO NOT contain a Texture folder. This can cause a memory leak similar to what you are experiencing.

Alastair

[Captain Savaloy]

Yes, I agree with Alastair, this situation can cause the exact problem.

I had the problem, and it turned out that an unknown scenery addon had placed a landclass file in the addon scenery/scenery folder, which of course has an associated texutre folder.

ANY landclass file placed in a folder that also has an associated texture folder will cause bad memory leaks.

Check out your scenery files.

Cap.

[PHCO]

Thank you very much for your help Alastair !

I don't have any landclass scenery folders with an texture folder. :-roll I have an additional question regarding your explanation --> Would that mean that the problem occurs everytime you're using the simulator or just if you're flying in the appropriate area the landclass-file is made for. My problem occurs irregular and seems to be a conflict between some addons (probably the FSD Piper Navajo) and another program.

[bill2759]

Ditto! I had the same problem. I thought it was my Ultimate Traffic addon. I could turn on the task manager and see the page file memory usage rising until it reached the limit, and then FS9 would crash to desktop. I wish I had known about the landclass option at that time. Nobody responded to my post when I described my problem. I wasn't even flying at the time, just plane watching at the major airports. I fixed it by deleting everything having to do with FS9 and reinstalling. I hope you can fix yours without having to go to such extremes. OHH! The pain.:-eek

[PHCO]

In the moment I am little bit frustrated - I just had another crash. I have cleaned all files in the addon-sceneries which I thought could cause the problem, but it happened again. I have made at least 20 test-flights it seems I only get this problem with the FSD Piper Navajo. Strange because I have flown this plane for at least 150 flight-hours without any problem. It must be a combination of something (maybe including US Roads) - re-installing the Navajo didn't help ... any ideas - I would appreciate any help !!! :-roll

[strungout911]

I too gave this problem with 1.5 GB.
And I Didn't know anyone else did too.

[shermank]

I don't know if this is the problem, but it very well could be connected to mesh created by Rob Gainer. Check to see if you have any, and delete it.

Sherm