alexmalvtk at gmail.com
Fri Sep 28 18:39:49 EDT 2012
It does not matter that you do not use code (vtkFieldData for example)
If you called New for a class which creates such objects internally
you will get them reported.
vtkDebugLeaks does not give you easy readable information where the
it is the best to use it from the scratch, so as soon new feature
added you can see that problem exist.
Try to disable as much code as possible and get to the point where no
leaks are reported, turn features on by small portions and test again.
On Thu, Sep 27, 2012 at 8:12 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> Without seeing your code, there is little we can do to help.
> On Thu, Sep 27, 2012 at 7:04 PM, cel02000 <cel02000 at yahoo.com> wrote:
>> Dear All,
>> After my code finishes, vtkDebugLeaks reports that it has detected leaks.
>> have attached the image of the report. I have checked my code carefully
>> all the vtk objects I used are removed by Delete() function. Could someone
>> give me some hints on how to detect these leaks? My code starts with low
>> and when it gets to the end of the code it uses 50GB of RAM!
>> One other thing I noticed is that vtkDebugLeaks reported there is some
>> instances of vtkCellData, vtkPointData, vtkInformation,
>> vtkInformationIntegerValue, vtkIdTypeArray, vtkFloatArray, and
>> which I have not used in my code.
>> I would appreciate any help.
>> View this message in context:
>> Sent from the VTK - Users mailing list archive at Nabble.com.
>> Powered by www.kitware.com
>> Visit other Kitware open-source projects at
>> Please keep messages on-topic and check the VTK FAQ at:
>> Follow this link to subscribe/unsubscribe:
> Unpaid intern in BillsBasement at noware dot com
> Powered by www.kitware.com
> Visit other Kitware open-source projects at
> Please keep messages on-topic and check the VTK FAQ at:
> Follow this link to subscribe/unsubscribe:
More information about the vtkusers