Hello Dimitris
Many thanks for your valuable information.
Can you say whether the leak you found is changed with the canvas size ?
Small canvas - small leak ?
Which operating system (NT4, NT5, Win95/8/Me) you are working on ?
How did you detect the program size ?
Thank you.
Valeri
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