I/we have been plagued by a bad memory leak in the DC code which in the last month or so prevented me/us from gathering large statistics online.It is not clear if this is the same that had plagued Jens Ivar or not. There is still another (much smaller) leak somewhere -- the BrDataTable object grow's as events are analyzed (one per bfs track approximately- a clue ?) -- The error message Warning in <TObjectTable::Remove>: 0x0a1a3f80 not found at 30366 Warning in <TObjectTable::Remove>: 0x0a1a4150 not found at 10538 shows up too. This of course only if you enable root mem control in the .rootrc file. The CVS code was updated as given (there may be a few more changes coming so the version was not tagged yet) // $Log: BrDC2DTrackFinder.cxx,v $ // Revision 1.7 2002/01/26 16:50:49 videbaek // Found a nasty memory leak in the DeleteTrack. // The bad trackcandidate was removed from the list that was an TObjArray. // This does not call the destructor of the object. This in contract to the // behaviour of TClonesArray where the destructor is called. // Nore the original code was written using TClonesArray. ------------------------------------------------------ Flemming Videbaek Physics Department Brookhaven National Laboratory tlf: 631-344-4106 fax 631-344-1334 e-mail: videbaek@bnl.gov
This archive was generated by hypermail 2b30 : Sat Jan 26 2002 - 12:39:05 EST