Message: DICOM example memory issue? Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question DICOM example memory issue? 

Forum: Documentation and Examples
Date: 14 Aug, 2012
From: Clare Huang <Clare Huang>

Hi all,

how's it going?!

I just recently ran a valgrind test on the example code of 'DICOM' in geant4.9.4.p02 version. I found some significant memory leak issue. See attached for the result from valgrind.

- i modified the dicom example into my own application and did encounter similar memory leak messages when ran the application with valgrind. The application will run properly for a 10-million run but after running 2-3 10-million runs, the application just got stuck and never finished the job.

- I tried to make sure all the dynamically-allocated variables are clear in the destructor. such as adding the line 'delete fZSliceHeaderMerged; delete fmateIDs' in the destructor of DicomDetectorConstruction class. However, the memory leak (definitely lost) still appear that there is some memory leak in DicomDetectorConstruction class as...

==1056== at 0x4A06205: operator new(unsigned long) (vg_replace_malloc.c:167) ==1056== by 0x4C1A187: DicomDetectorConstruction::ReadPhantomDataFile(G4String const&) (in /home/shuang/geant4/tmp/Linux-g++/dicom/

or should i focus on clearing other memory leak points before getting to the one above? there are a number of G4 class-related memory leak, and I am not sure how i can correct those...

can someone shed some light how to tackle this memory leak problem? thanks a lot for your time and help in advance.

Best regards, Clare

Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 None: Re: DICOM example memory issue?   (Clare Huang - 14 Aug, 2012)
 Add Message Add Message
to: "DICOM example memory issue?"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews

[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]