RC 3.4 memory consumption

[Müller]

It is normal for the use of more than 6gigas of memory, only with the FG in multiplayer?
Running only the FG as time was increasing memory usage, I began with 53% and in the first hour has increased to about 70%, and in the second hour consumption was 89%, it never occurred to me that in previous versions, I had installed the 3.0 version and I can remember working below 70%.
The aircraft used for longer were 748 and 707 (this I used with low memory consumption in version 3.0).

C:\Program Files\FlightGear 3.4.0\bin\fgfs.exe
--fg-root=C:\Program Files\FlightGear 3.4.0\data
--fg-scenery=C:\Users\xxxxxx\Documents\FlightGear\TerraSync;C:\Users\xxxxxx\Documents\FlightGear\Custom Scenery;C:\Program Files\FlightGear 3.4.0\data\Scenery
--terrasync-dir=C:\Users\xxxxx\Documents\FlightGear\TerraSync
--fg-aircraft=C:\Users\xxxxxx\Documents\FlightGear\Aircraft
--airport=SBPA
--aircraft=707
--disable-random-objects
--disable-ai-models
--disable-ai-traffic
--enable-real-weather-fetch
--fog-disable
--bpp=32
--timeofday=noon
--enable-terrasync
--disable-fgcom

[Thorsten]

It is normal for the use of more than 6gigas of memory, only with the FG in multiplayer?

The memory consumption is about 0.7 GB + c1(Aircraft) + c2(Terrain) * visibility^2

where c1(Aircaft) mesaures how heavy your aircraft is in memory and c2(Terrain) measures what vertex density the terrain has. Dependent on what the visibility is and what terrain you're running and what LOD settings you're using for trees, buildings and objects, the total consumption can be below 3 GB even for a heavy airplane (30 km visibility in 1.0 World Scenery) or equally well exceed 12 GB (160 km visibility in CORINE-based Europe).

There is no 'normal' - it depends almost exclusively on your settings.

[Müller]

https://www.dropbox.com/s/i8w679nhy4cyng9/FG.jpg?dl=0

[Thorsten]

I hope you don't expect me to look at this screenshot and tell you whether your memory occupancy on a long flight is normal.

[Müller]

There is no need for you to tell me if this is normal or not, the image speaks for itself, doesn't it?

[wlbragg]

I began with 53% and in the first hour has increased to about 70%, and in the second hour consumption was 89%

I'm not sure how much help this is because I have never even looked at my memory usage in MP or flown that long but once or twice in MP. But I can say that doesn't sound good if it just keeps climbing, because eventually you come to crawl or crash.

Questions I would have are...
Did the memory usage eventually level off?
Did you have other CPU tasks going on in the background?
Can you reproduce these results with the same settings and aircraft?
Can you reproduce these results with the same settings and different aircraft?
Can you reduce this usage with modifications to the settings and the same or different aircraft?

I guess what I am getting at is I would try a bit more debug and tweaking and see if you can control the usage or if it grows regardless of what you do.

[Müller]

Hi wlbragg,
I started the flight airport SBGL with Beluga aircraft = 33%
After 2 hours and 45 minutes, finished the SBPA flight with 68%
Same settings used in my previous post.
These percentages were obtained only with FG working, no other program open.
I need to wait for more people to post their results

[wlbragg]

I started the flight airport SBGL with Beluga aircraft = 33%
After 2 hours and 45 minutes, finished the SBPA flight with 68%

Did it get to 68% early on and then level off or did it keep gradually climbing to 68% throughout the flight and was still climbing when you quit the test?
If it is the latter then I'd say there is a leak or at the very least were not managing the memory well enough.

[Philosopher]

Can you try two things? Try circling the same area for a long period of time to see if the memory goes up. And whenever you think the memory usage is very high, click the button "Reload Scenery" in the Debug menu and see if the memory usage goes down.

[Müller]

Beginning of the flight with 33% and has been climbing gradually flight was closed with 68%

[Müller]

"Reload Scenery" .

I've done, without any positive result

[Müller]

Flight of 2hours and 32 minutes - not multiplayer - Aircraft 707:
Total memory consumption: 5.39 gigas
CPU 19%
fgfs.exe: memory consumption, 3 gigas, 680 megas 132 kb, and was gradually increasing, i do screenshot....and crash, closed program
The issue is not the total consumption of FG (2, 4, 8 gigas), but in that moment will stabilize this memory consumption

[wlbragg]

Unfortunately at the moment I can't help you out with a comparison of my system by trying to duplicate or reproduce your problem because I am running some other jobs on my CPU. But when they are done I can try a long flight and see how my memory is handled in comparison to yours.
Anyone know of any existing memory leak issues?
Anything reported to bug tracker?

You can try bare bones setup and see if you can ever get it stable. If you can then proceed to turn things on one by one and try to find the issue.

[Thorsten]

There is no need for you to tell me if this is normal or not, the image speaks for itself, doesn't it?

No, in fact it doesn't.

We can swap stories all day long - how I managed to use 12 GB when I accidentially had building and tree density maxed out in hires scenery and ran into swap flying into the French Alps - and amazingly enough, it was still flyable. Or how going into space caused me to hit 9 GB, but then FG cleaned up and the occupancy dropped down to 7 and everything was nice and smooth again. The point is - what do you learn from me telling you that? I assume close to nothing - and similar with you telling stories about this one situation.

The point is that if you want to learn something, you need to set up a benchmark test situation. Note the quantity you're interested in. Change one setting. Repeat the benchmark. Make a table of what setting changed memory occupancy how. Then you know something.

fgfs.exe: memory consumption, 3 gigas, 680 megas 132 kb, and was gradually increasing,

Well, that's definitely not on the high end - even fits into 32bit systems...

[Müller]

No, we're not going to swap stories all day, one thing became very clear if i continue in the FG, my next computer will have 32 gigas of memory to run " clean", "soft", with '"only" 28 or 24 gigas.