Curt, I do remember seeing something similar happening, on a long haul test flight between Tokyo and Sydney, which judging from the timestamp on the scenery directory, I did around the 22nd of June. Same problem: Huge memory leak, up to the point where the aircraft became uncontrollable. I reran the same route the next day, and nothing happened. Weird. Anyways, hope that the date of my problem flight may be of any help finding this bug.
Actually, I'm testing long range performance right now, doing a 10 hour KSFO to EHAM trip. Memory use appears to be rock solid. Cheers, Durk On Sunday 18 July 2004 21:05, Curtis L. Olson wrote: > 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!!!! > > Thanks, > > Curt. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
