Martin Spott wrote:
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.

Can anyone confirm similar experience ?

If you want to hear a strong opinion about Flightgear's memory management, simply run the following:

        # valgrind fgfs


--------- Boris

_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] 2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to