Paging file (XPSP3 Pro, FS2004)

Dimon · Post by **Dimon** » Sat Jul 05, 2008 8:33 pm

martin[flytampa] wrote:
Dimon wrote:Check the swap size BEFORE the session and AFTER. I have 700GB at the start and 1680GB at the end.
You mean you're looking at the "pagefile.sys" in windows explorer?
I have mine set to a fixed size at the moment.

No, I mean looking at Win Task Manager/Performance Page, where CPU and PF usage shown. You need to monitor PF usage during AI spotting - that's all.

BTW, my paging file is also set to fixed size 6GB (while having 4GB of physical memory).

Post by **martin[flytampa]** » Sat Jul 05, 2008 8:47 pm

I'm flying circles over HK city in the Cessna now with AI-enabled but the FlyTampa-HongKong/texture/ folder renamed. Scenery loads all white, perhaps it is just a texture file.

Dimon · Post by **Dimon** » Sat Jul 05, 2008 8:51 pm

Is PF growing in size?

Post by **martin[flytampa]** » Sat Jul 05, 2008 9:03 pm

No FS9 Ram stayed at 300MB, pagefile at 500MB, but I need to try the same thing again with static aircraft and AI ships installed... and keep in mind that was all untextured.

Dimon · Post by **Dimon** » Sat Jul 05, 2008 9:44 pm

Ok - thanks for the great support, Martin.

Jure · Post by **Jure** » Sun Jul 06, 2008 12:48 am

I'll jump in here with my observations:

Made a full flight with a RFP/Posky B747-200 from Dubai OMDB to Kai Tak. I fly this aircraft all the time and have had no problems whatsoever in the past. As I approached Hong Kong I refreshed the scenery and all went well. Landed, exited the runway and then played the replay for, oh, 20 times, LOL. Spot view, tower view, taking screenshots and whatnot. When I arrived at the gate I again went to spot view and looked around quite a lot. I had AI at 100% with almost all parking spots filled. Suddenly, POOF! an OOM error and that was it. Happened for the second time EVER for me.

Second flight was Hakodate RJCH to Kai Tak aboard the PMDG B747-400. This time I stayed in the (virtual) cockpit on approach to VHHX and PF usage was hovering around 1.1 Gb just before final approach - which is normal for this bird and complex scenery. No replay, straight to the gate, shutting the engines down and only then I went to spot view, to see how things were. PF grew to almost 1.7Gb in certain conditions (looking towards the parking area from the treshold of rwy13) and shrunk to 1.4 when I turned the other way (towards the city)

Clearly, there is so much to display that the system chokes with excessive view changes. Wing views, spot views, tower views, full AI and Kai Tak with so many buildings.... my advice is to stay in the pit and fly the darn plane instead of gawking around, LOL!

I'll make another flight and report back. BTW, I used the 9D Kai Tak prior to FT version and I triple checked to have removed every trace of it.
Running an AMD FX57, nVidia 7800GTX, 2GB RAM (Hey Paul!

)

Regards,
Jure

Post by **martin[flytampa]** » Sun Jul 06, 2008 2:40 am

Memory leak Test-Patch.

www.flytampa.org/dwl/FlyTampa_HongKong_FS9_MemFix.exe

Dimon · Post by **Dimon** » Sun Jul 06, 2008 8:12 am

martin[flytampa] wrote:Memory leak Test-Patch.

www.flytampa.org/dwl/FlyTampa_HongKong_FS9_MemFix.exe

Just completed the test after applying the patch.

Loaded MRAI AI Spotting Utility with full AI at 10:00GMT (dusk at VHHX): PF~760GB. Then ran x2 acceleration and after 20 minutes of spotting PF became ~ 1478GB.

Post by **george[flytampa]** » Sun Jul 06, 2008 11:03 am

Dimon wrote:
Loaded MRAI AI Spotting Utility with full AI at 10:00GMT (dusk at VHHX): PF~760GB. Then ran x2 acceleration and after 20 minutes of spotting PF became ~ 1478GB.

How does the Fs9.exe memory usage look after 30mins of use. The figure under the process tab in Task Manager.

Mines staying relatively static after this fix. Before it grew an additional 1.2GB within an hour & crashed(OOM).

Now all seems well. I've had it circling the airport on 4x time for 1.5hours this morning.

Dimon · Post by **Dimon** » Sun Jul 06, 2008 1:01 pm

Just completed test #2

First of all - it seems like MRAI Traffic Monitor Utility combined with Active Camera generates huge memory leak by itself. I switched to default Cessna and compteled exactly the same test as decribed above. PF grew from 0.811GB to 1.1GB for 5 munites and remains between 1.06-1.13 for another 40 minutes, the result that I consider OK.

Thus - it seems like the puzzle solved. Again, thanks a lot for the quick fix and support.

Henry777 · Post by **Henry777** » Sun Jul 06, 2008 3:11 pm

After installing the fix, I made the following test.

- Loaded ASv6.5 with current online weather
- Loaded PMDG 747 and parked at stand 15, all engines off, APU running
- AES is enabled
- AI traffic 20% (MyTraffic)

Then I checked the process memory of FS9 - 858MB. After 40mins the process memory grew up to 1.5GB. It took much longer to reach that memory usage then before the patch, but it seems that the problem still exists.

Dimon · Post by **Dimon** » Sun Jul 06, 2008 6:29 pm

Unfortunately, I do confirm the last post.

This time I did the easiest thing - load VHHX with default Cessna, ASV and 100% trafftc (PF at this moment was ~700/800MB)...and went to gym for 1.5 hours. When I came back, PF was almost 1.6GB.

Dimon · Post by **Dimon** » Sun Jul 06, 2008 7:09 pm

Martin,

I looked into patch content - it's only landclass file included. not textures. Correct?

Post by **george[flytampa]** » Sun Jul 06, 2008 7:13 pm

Dimon wrote:Martin,

I looked into patch content - it's only landclass file included. not textures. Correct?

Yes. no textures.

Your numbers look normal to me. 1.5GB swapfile I get over default Heathrow in 5mins.

Check the fs9.exe usage again. You are not getting crashes/OOMs anymore right?

By PF do you mean pagefile or Page faults?