Hey guys,

Did we introduce a memory leak when paging scenery recently? I left FG running all night (with ATC and AI traffic disabled) and memory usage was stable. Then I went for 2-3 hour flight and just about filled up all my main RAM + Swap on my linux machine before I finally killed landed and exited. I know we were very careful when we set this all up to make sure memory usage was stable during scenery paging and that we didn't leak any memory, but something seems to have crept in along the way with one of the changes. The only thing I can remember recenly is support for terrain/object separation in the directory structure and some sort of simplistic state presorting when loading terrain. Could one of those things be doing this? Has anything else changed? This is not good if someone wants to do long flights!!!!



Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d

_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to