Hello,
after reading a LWN article I started playing with the memory
ovcercommit switch on a Linux box. Later I wondered why I wasn't
unable to run FG reliably anymore and ran a 'top' to see what's going
on here. I noticed that FG appears to lock huge amounts of memory - and
the X server as well.
Martin Spott wrote:
Hello,
after reading a LWN article I started playing with the memory
ovcercommit switch on a Linux box. Later I wondered why I wasn't
unable to run FG reliably anymore and ran a 'top' to see what's going
on here. I noticed that FG appears to lock huge amounts of memory - and
Boris Koenig wrote:
If you want to hear a strong opinion about Flightgear's memory
management, simply run the following:
# valgrind fgfs
Oh yeah:
quickstep: 18:07:42 ~ valgrind /opt/FlightGear/bin/fgfs
[... lots of stuff I probably might want to have a look at ]
disInstr:
Is this by any chance related to the poor framerate that some of us have?
Ampere
On October 1, 2004 12:09 pm, Martin Spott wrote:
Boris Koenig wrote:
If you want to hear a strong opinion about Flightgear's memory
management, simply run the following:
# valgrind fgfs
Oh yeah:
