Memory leak viewing DICOM tree

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Load the attached images in the binary version of Dicompyler.
2. Select the DICOM Tree plugin and load a CT file.
3. Program freezes(see attached image), memory usage increases over time(not 
quickly).

What is the expected output? What do you see instead?
Normal Dicom Tree plugin, see attached for what is seen. Also attached is a 
separate log file that was being recursively created during the "leak".

What version of the product are you using? On what operating system?
Dicompyler 0.4.1-1 binary, Win7 64 bit.

Please provide any additional information below.
This problem is not occurring for me in python.

Original issue reported on code.google.com by lstrd...@gmail.com on 7 Jan 2012 at 2:28

Attachments:

• memleak.png
• dicompyler.log.6
• 1.dcm
• 2.dcm
• 3.dcm

[GoogleCodeExporter]

This is a bug that I found recently and fixed in r69a9c3ae274b. It occurs 
somehow in binary builds because of redirection of stdout/stderr to the logging 
system. I am not sure what causes the recursion exactly, thus the redirection 
in that patch has been set to /dev/null.

I can reproduce your bug with the 0.4.1-1 binary on the Mac with my own data as 
well as yours. I had not seen it on Windows, and actually thought it was 
restricted to the Mac builds.

The next release will include this fix.

Original comment by bastula on 7 Jan 2012 at 2:39

• Changed state: Fixed