|Message: DICOM example memory issue?||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
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/libdicom.so)...
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:||Outline Depth:||Add message:|