Re: [Flightgear-devel] Valgrind logs

[Torsten D. <To...@t3...>]

> Hello everybody,
> 
> a valgrind log of recent FlightGear is available from
> http://dl.dropbox.com/u/15761796/valgrind.log
> (13 MB). A short version containing only the "definitely lost"
> backtraces is at
> http://dl.dropbox.com/u/15761796/definitely_lost.log
> (59 kB).
> 
> The largest single entry stems from the TrafficMgr code. It is fixed by
> the attached patch, which deletes all scheduled flights.
> 
> However, as I quit the program as soon as the 3D clouds showed up, I
> suspect that with increased run time other leaks might become more
> important, possibly the ones regarding
> simgear/scene/model/SGReaderWriterXML.cxx:289.
> 
> Some things that might be fixed relatively easy:
> FG/src/Autopilot/digitalfilter.cxx: all InputValues pushed_back to one
> of the InputValueLists need to be deleted
> FG/src/Autopilot/digitalfilter.cxx:316: members of componentForge need
> to be deleted
> FG/src/Autopilot/autopilot.cxx:46: the same
> FG/src/Instrumentation/gps.cxx:1575: _currentWaypt needs to be deleted
> FG/src/AIModel/performancedb.cxx:88 members of _db need to be deleted
> 
> Hope this helps a little in stuffing the sieve,
> best regards,
> 	Andreas
> 
Thanks for looking into this.
A few comments on the autopilot objects:
InputValueLists are vectors of InputValue, a subclass of SGReferenced, so they 
should be automatically deleted, once the last reference is gone?

The componentForge is a static vector, initialized only once at startup. It's 
intention is to live during the entire session. It's never dropped, never 
recreated and never cleared. 

Torsten