|Message: Memory Leak or Not?||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)|
Dear Geant4 People, During the compilation of our simulation program, the val-grind memory leakage check tool found three memory leakage problems, which were about the creation of new variables by some Geant4 10.1.2 functions. I wonder if 1) These variables are deleted by Geant4 at the end, so users do not have to worry about, 2) users should delete them by themselves (then how?), or 3) the assigned memory space gets simply lost. Your help would be greatly appreciated. I attached the warning messages from the val-grind below. Regards, Doris --- Start of Error Messages --- Case 1) 1,320 (200 direct, 1,120 indirect) bytes in 1 blocks are definitely lost /tmp/valgrind-3.8.1/coregrind/m_replacemalloc/vg_replace_malloc.c:298 operator new(unsigned long) /home/Linux_x86_64/opt/lib/libG4run.so G4RunMessenger::G4RunMessenger(G4RunManager*) /home/Linux_x86_64/opt/lib/libG4run.so G4RunManager::G4RunManager() /home/simulation/src/RunManager.cc:xxx RunManager::RunManager() Case 2) 1,014 (200 direct, 814 indirect) bytes in 1 blocks are definitely lost /tmp/valgrind-3.8.1/coregrind/m_replacemalloc/vg_replace_malloc.c:298 operator new(unsigned long) /home/Linux_x86_64/opt/lib/libG4physicslists.so G4OpticalPhysicsMessenger::G4OpticalPhysicsMessenger(G4OpticalPhysics*) /home/Linux_x86_64/opt/lib/libG4physicslists.so G4OpticalPhysics::G4OpticalPhysics(int, G4String const&) /home/simulation/src/SimulationModule.cc:xxx SimulationModule::initialize() Case 3) 2,928 bytes in 61 blocks are definitely lost /tmp/valgrind-3.8.1/coregrind/m_replacemalloc/vg_replace_malloc.c:298 operator new(unsigned long) /home/Linux_x86_64/opt/lib/libG4processes.so G4ElectroNuclearCrossSection::GetElementCrossSection(G4DynamicParticle const*, int, G4Material const*) /home/Linux_x86_64/opt/lib/libG4processes.so G4CrossSectionDataStore::GetCrossSection(G4DynamicParticle const*, G4Element const*, G4Material const*) /home/Linux_x86_64/opt/lib/libG4processes.so G4CrossSectionDataStore::GetCrossSection(G4DynamicParticle const*, G4Material const*) /home/Linux_x86_64/opt/lib/libG4processes.so G4HadronicProcess::GetMeanFreePath(G4Track const&, double, G4ForceCondition*) /home/Linux_x86_64/opt/lib/libG4processes.so G4VDiscreteProcess::PostStepGetPhysicalInteractionLength(G4Track const&, double, G4ForceCondition*) /home/Linux_x86_64/opt/lib/libG4tracking.so G4SteppingManager::DefinePhysicalStepLength() /home/Linux_x86_64/opt/lib/libG4tracking.so G4SteppingManager::Stepping() /home/Linux_x86_64/opt/lib/libG4tracking.so G4TrackingManager::ProcessOneTrack(G4Track*) /home/Linux_x86_64/opt/lib/libG4event.so G4EventManager::DoProcessing(G4Event*) /home/simulation/src/RunManager.cc:xxx RunManager::processEvent(int) --- End of Error Messages ---
|Inline Depth:||Outline Depth:||Add message:|