On Wednesday 27 September 2006 22:42, Durk Talsma wrote: > On Wednesday 27 September 2006 22:07, Frederic Bouvier wrote: > > Yeah, that's what I thought initially as well, but it doesn't look like it. > I added the delete statement in the distructor, and still have the leak. > > FWIW, I don't believe so strongly that it's actually a leak in the AI > system itself, although the AI system may be causing it. My best lead > sofar, is the fact that I completed two intercontinental flights using the > CVS version of flightgear after I uncommented one line of code in > src/Airports/simple.cxx >
Regarding this mysterious memory leak, I thought I'd give a quick heads up: I've disabled some parts of the new AI distance tracking code, and FlightGear appears to run stable again. I have the full AIModels code running and also have the ATC controller switching mechanism active. All I have disabled is the code that does the actual checking. This narrows down the possibilities, and I'm pretty optimistic that I have an idea of what's going on by the weekend. So it looks like there is something in the new AIDistance checking code that blows up something in FlightGear. I'm still puzzled what it can be though, because all the memory allocation / deallocation is done by stl vector push_back() and erase() mechanisms. Cheers, Durk ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
