Stephane Tourneur <tourneur@fnal.gov> writes: > There is apparently a memory leak that causes the ROOT browser to > take more and more memory until it saturates (after only three screens of > histograms have been displayed...), apparently because of a lack of > memory. It is obvious by using the unix 'free' instruction that the > Root browser takes almost all the RAM available, what makes it very > very slow to display new screens of histograms. > I'm not expert in memory leak problems at all, and have big difficulties > to solve this problem. Could anybody with some experience ih this > field help please? > This is an important issue because it hinders the works of the CDF offline > monitoring shift a lot. > Thanks in advance for any help! > > Stephane Hi Stephane, to find out which objects are accumulated you can inspect gObjectTable (gObjectTable->Print()). Also the size of the leaked memory could give you a hint what is not freed. There are many memory debuggers available I used ccmalloc for example. It keeps track of all memory allocations and deallocations and makes statistics out of it. Its homepage is at http://www.inf.ethz.ch/personal/biere/projects/ccmalloc/ Jiri
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:51:00 MET