Dear Dimitris
I have been running gPad->Update() for 1'000'000 times with no indication
of the memory leak.
By this reason I'd like you provide further information on the figures you present.
Did you mean running your let's say "Graph->Fit(...) " 100 times one will get the program
memory growing by 348K * 100 = 35 Mb ?
Did you observe the memory leak with the "pure" ROOT executable or it is a feature
of your MFC base code only ?
Thank you
Valeri
----- Original Message -----
From: Dr. D. Sideris <d.sideris@ic.ac.uk>
To: <roottalk@pcroot.cern.ch>
Subject: [ROOT] Memory Leaks
Dear Rooters,
I am trying to tie down an application which is written in VC++6 using ROOT and MFC in win NT. I seem to be getting memory leaks
in many operations which are associated with canvases. I step through each command in the program with the debugger and watch
whether there is an increase in the size of the program that is not reversed when a given process is finished. As an example I
open a small canvas with one pad I create a TGraph object with a small array of points and then I perform a fit to those points.
The I plot the results. Below are commands which take memory and never return it:
TPaveLabel *pave = new .... -> 4k
Graph->GetXaxis()->SetTitle.... -> 200k
Graph->Fit(...) -> 348k
canvas->update -> 100k
I'm not hasty to hold root responsible for those leaks, because sometimes there are other inconsitencies in the coding which
cause indirectly innocent calls to leak. However because my application doesn't seem to leak anywhere else appart from the
neighbourhood of canvases, that narrows it down. If someone has any good advise I'd be gratefull.
Regards
Dimitris
P.S. I use root version 2.25/03
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:41 MET