[Insight-developers] Memory leaks after reading some dicom files
kent williams
norman-k-williams at uiowa.edu
Wed Mar 21 16:42:41 EST 2007
If you can send me a link to one of the image series that is causing the
memory leaks I can run it under valgrind and try and see what¹s leaking.
How are you diagnosing the memory leaks? Any idea where in the code they¹re
happening?
On 3/21/07 4:07 PM, "Massimo Esposito" <mass.esposito at gmail.com> wrote:
> Hi list,
> i have a problem. My application reads dicom files but when i close it i
> detect memory leaks .
> I used itk 2.4 and i didn't have this problem. Now i ported my code to itk 3.0
> or itk 3.2 and i detected this strange behaviour.
> But it happens only with some series, that is, sometimes, after having opened
> some dicom files, i can close my application correctly, sometimes memory leaks
> are generated (i noted to have problems with file without extensions, but
> maybe it is casual).
> I tried to read these dicom files that generated memory leaks and then to
> write them using GDCM embedded in itk. If i read this files written with GDCM
> no memory leaks are generated.
> Besides, if i try to use itk::DicomImageIO2 instead of itk::GDCMImageIO no
> memory leaks are generated in any cases, but using itk::DicomImageIO2 i can't
> read all the header dicom's tags.
> Instead, using itk::GDCMImageIO, i do it. Moreover, if i call the
> updateoutputinformation member instead of update one of the reader, the
> number of memory leaks is lower but still present.
> So i think there are some problems about reading the dicom header.
> My code worked fine with itk 2.4!!
> Can someone help me?
> Thanks a lot,
> Max
>
>
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.itk.org/mailman/private/insight-developers/attachments/20070321/84bb0d0c/attachment.htm
More information about the Insight-developers
mailing list