I have never before, ever, suffered from an OOM, the one actually reported as such by FSX. But since late last week I cannot complete a standard test flight, one flown hundreds of times before, without an OOM while circling EGLL for an approach, travelling from EGCC.I've tried with no addon scenery, I've tried wth no AI traffic, I've tried with sliders reduced and no autogen.Monitoring the virtual memory avasilable to FSX, in my normal configuration, it starts with about 2.4Gb free, 1.6 Gb used. When underway that depletes a bit, down to aroound 1.8-2 Gb free, for most of the route, going up a little sometimes as well as down. But then, within about 30 nm of EGLL (even with no add-on EGLL scenery, low autogen, no VFR London, etc), the free memory is depleting at the rate of about 3 Mb per second. Within 10 minutes, and way before touchdown (I'm going for 27R from BNN), the OOM is reported.I've used VMMAP to compare memory use then with what it was like at the start, and the biggest single change is the filling of the upper space by thousands of "Private" areas, (allocations from heap), all of the same size 1772kb, or 0x1C0000 bytes.I used a debugger to peer inside these blocks, and every one I looked into is full of text like the following:$00::*::*::097,009,-13.2/097,009,-18.6/097,009,-21.5/086,012,-30.1/025,028,-36.4/009,045,-45.8/003,049,-52.5/004,036,-47.2/001,030,-45.3$002::*::*::173,015,-06.9/132,019,-11.6/138,015,-13.6/128,010,-23.9/064,012,-35.5/048,015,-45.7/035,012,-48.1/022,012,-44.7/359,012,-43.7$003::*::*::226,028,-10.2/214,030,-13.4/220,026,-15.5/223,013,-25.0/213,011,-37.5/220,012,-45.7/244,022,-45.0/252,020,-42.4/263,018,-42.0$004::*::*::324,019,-04.5/297,022,-11.1/290,026,-12.1/281,032,-18.3/272,035,-29.8/266,058,-38.5/269,071,-50.8/267,061,-49.7/268,046,-45.6$005::*::*::332,021,04.4/321,023,01.3/313,026,-01.0/291,038,-09.5/285,053,-21.1/283,054,-31.6/283,063,-47.1/284,073,-57.0/278,057,-53.9$006::*::*::312,028,08.8/316,027,05.8/316,028,02.9/315,029,-08.1/309,037,-18.1/304,043,-29.0/303,047,-44.9/296,053,-53.7/289,053,-57.4$007::*::*::073,035,12.5/064,035,06.9/052,038,04.5/011,048,-02.2/348,028,-14.3/341,030,-26.1/354,025,-42.0/354,028,-52.3/328,027,-57.2$008::*::*::081,019,22.3/083,021,17.4/079,020,15.0/066,014,06.5/057,021,-05.0/053,015,-15.6/146,005,-31.3/155,007,-41.8/236,004,-54.1$009::*::*::069,020,21.2/075,014,16.8/053,006,14.7/037,008,07.3/051,020,-04.6/068,011,-16.9/006,006,-31.6/329,009,-42.3/311,015,-54.2$010::*::*::084,017,20.1/074,016,15.9/060,015,13.9/034,011,06.8/342,019,-05.7/295,012,-17.8/325,024,-33.5/306,027,-42.9/303,032,-54.5That's just a tiny sample from one of those blocks.Now I've no idea what part of FSX, or what add-on, might be generating these, or using them. Does anyone here recognise the data type at all? Or at least know who I might ask? If I could identify the source I've a chance of fixing it -- nothing else I've tried makes any difference so far!I'll check in the developers forum too.Thnaks for any ideas!RegardsPete

Edited February 23, 201214 yr by Pete Dowson

I know I wrote this before in this thread, but I've managed to fly about five straight long distance flights now with almost all graphic settings cranked right up including Extreme Scenery Complexity and Extreme Autogen with an lod of 6.5 and I haven't suffered one single OOM.It does appear for me at least that going back and forth from full screen to windowed will eventually cause an OOM. If I only ALT-ENTER about 3-4 times during a flight I won't suffer an OOM.

"Excuse me. Before I got paid to, uh, speak French, I, uh, I used to read maps. This first number is a longitude...Two sets of three numbers. Degrees, minutes, and seconds. The first number has three digits and the last two are below sixty. Obviously, it's not in the right ascension and declination on the sky. These have to be earth coordinates."LOL!! Sorry about that, Pete! But after seeing your debugger findings, the scene from "Close Encounters of the Third Kind" immediately came to mind. Could those numbers actually be longitude/latitude scenery files? I have no clue but it may be worth a shot throwing it out there.

"Excuse me. Before I got paid to, uh, speak French, I, uh, I used to read maps. This first number is a longitude...Two sets of three numbers. Degrees, minutes, and seconds. The first number has three digits and the last two are below sixty. Obviously, it's not in the right ascension and declination on the sky. These have to be earth coordinates."LOL!! Sorry about that, Pete! But after seeing your debugger findings, the scene from "Close Encounters of the Third Kind" immediately came to mind. Could those numbers actually be longitude/latitude scenery files? I have no clue but it may be worth a shot throwing it out there.

actually, after sending the question out to a few colleagues, I got the answer. It IS weather data, from ActiveSky's weather snapshot files! It turns out to be a memory leak in one of my own experimental programs I'd forgotten about, one to get the QNH for a destination airport for Radar Contact.All fixed now thanks to the rapid response from Damian Clark of Hifi! Thanks Damian.RegardsPete

So Pete,Is it Active Sky data causing the problem?Kind regards,

That's great news, Pete!

Pete, can the REX weather engine also cause this?

Or, like I've asked before, does FSX have an inherent leak because, although my oom's have ceased, when I land at the destination airport, the vas is at about 3.5, so I haven't dared to continue flying to a new airport without quitting FSX, since I have noticed that the vas doesn't decrease even after departing an airport.

Edited February 25, 201214 yr by kjjj11223344

I found something interesting that stopped my OOM's for FSX.When I fly, I usually switch back and forth between windows and full screen more than once and eventually I would get an OOM because every time I switch between windowed and full screen, FSX uses up another 200-400 MB of RAM and doesn't release it. So eventuallu it runs of out memory around 3.4 GB.I was using the alternate frame limiter with the d3d9.dll and antilag files in the FSX folder. Just now, I switched back to the frame limiter that uses the batch file to set the limited frame rate and now I'm not getting OOM's and when I switch between windowed and full screen, FSX is not gaining RAM usage like it did with the alternate limiter.I just some a few quick flights, but my RAM usage stayed low and I have almost everything cranked right up in FSX. Before I would change between windowed and full screen just sitting at a runway and I would eventually get an OOM. But not anymore.

I found something interesting that stopped my OOM's for FSX.When I fly, I usually switch back and forth between windows and full screen more than once and eventually I would get an OOM because every time I switch between windowed and full screen, FSX uses up another 200-400 MB of RAM and doesn't release it. So eventuallu it runs of out memory around 3.4 GB.I was using the alternate frame limiter with the d3d9.dll and antilag files in the FSX folder. Just now, I switched back to the frame limiter that uses the batch file to set the limited frame rate and now I'm not getting OOM's and when I switch between windowed and full screen, FSX is not gaining RAM usage like it did with the alternate limiter.I just some a few quick flights, but my RAM usage stayed low and I have almost everything cranked right up in FSX. Before I would change between windowed and full screen just sitting at a runway and I would eventually get an OOM. But not anymore.

Great observation. I too have noticed the same thing, and thus I've had to alt+tab if I want to switch windows. I don't have time today but I will try reverting to the batch file fps limiter on my flight tomorrow. Maybe this will not only fix the vas increasing and never going down while using alt+tab, but it might allow FSX to release vas after I fly away from a specific airport.

Okay, I just tested and it was the antilag fps limiter causing the problem. I fired up fsx, switched from full screen to windowed mode a couple of times, loaded a couple of different airports, and the apparant memory leak wasn't there anymore. My VAS never went above 2.4gb, and that is with the ngx, rex, and fsdreamteam airports. So, WallysWorld, I couldn't have done it without you. I can now complete multiple hops without having to restart fsx. Once again, I am highly thankful.

Glad to hear it worked out for you too. It was a big headache!

i was wondering what this means using a batch file frame rate limiter? i am having all sorts of omm problems just want them to stop!!

I too am having OOM galore at the moment. Never happend before. The only recent things I've purchased and installed (last couple of months) are FSDT KLAX, FSDT PHNL, FS2Crew NGX Voice commander, AS2012 and updated to latest versions of FSUIPC. I've lowered my LOD down and reduced my settings to moderate. I have a I7920@ 4.2Ghz 6GB DDR3 Ram and GTX580Sc. This happens when flying in stock scenery around the UK.

 

Only really noticed them over the past month. Also getting a Fatal error everytime I quit FSX.

 

Any help is much appreciated.

I too am having OOM galore at the moment. Never happend before. The only recent things I've purchased and installed (last couple of months) are FSDT KLAX, FSDT PHNL, FS2Crew NGX Voice commander, AS2012 and updated to latest versions of FSUIPC. I've lowered my LOD down and reduced my settings to moderate. I have a I7920@ 4.2Ghz 6GB DDR3 Ram and GTX580Sc. This happens when flying in stock scenery around the UK.

 

Only really noticed them over the past month. Also getting a Fatal error everytime I quit FSX.

 

Any help is much appreciated.

 

Best that you post this as a new post. Also post details of the Event Viewer which posts details of each crash. What was the fatal error? Make sure your MSV's and dotnet framework software is up-to-date. When you installed the new software, did you disable UAC and any anti-virus program until the installation is completed? Are you using Windows 7 32 bit or 64 bit?

 

Best regards,

Jim