Problem 2164 - Memory usage for /grdm/sourceTimeProfile
Summary: Memory usage for /grdm/sourceTimeProfile
Status: RESOLVED FIXED
Alias: None
Product: Examples/Extended
Classification: Unclassified
Component: radioactivedecay/rdecay02 (show other problems)
Version: 10.5
Hardware: PC Linux
: P4 normal
Assignee: dennis.herbert.wright
URL:
Depends on:
Blocks:
 
Reported: 2019-05-15 12:38 CEST by matteo.centis.vignali
Modified: 2020-01-22 20:37 CET (History)
2 users (show)

See Also:


Attachments
Run macro to show the described behavior (531 bytes, text/plain)
2019-05-15 12:38 CEST, matteo.centis.vignali
Details

Note You need to log in before you can comment on or make changes to this problem.
Description matteo.centis.vignali 2019-05-15 12:38:00 CEST
Created attachment 570 [details]
Run macro to show the described behavior

Hello,
I am using geant4.10.05 on a Ubuntu 16.04.6 machine.
I need to bias the decay of radioactive nuclei, and I used the command
/grdm/sourceTimeProfile

When the command is used, the memory used by the program increases with time, leading eventually to a crash if the number of events is large enough.
When the command is not used, the memory usage is constant in time.
I monitored the memory usage using htop.

I could confirm this problem with the example rdecay02 and the attached file, derived by the macro isotopes.mac provided with the example.
By uncommenting the line
/grdm/sourceTimeProfile macros/beam.data
the effect can be seen.

Best regards,
Matteo
Comment 1 dennis.herbert.wright 2020-01-22 20:37:49 CET
I fixed a major memory leak in G4Radioactivation.  rdecay02 now leaks 60% less memory.
The size of the application still grows with time, but I think its source is elsewhere.