Memory leaks in MAUS
At CM38 Adam mentioned a slow memory leak in MAUS.
Indeed, there do seem to be leaks.
On my machine, running offline reconstruction on a smallish data-set [ 04995.000 ], the memory usage climbed from 180MB to 550MB
[ memory monitor log attached ]
Valgrind shows some stuff coming from Python, ROOT and GEANT.
On the MAUS side, there seem to be lots of leaks from G4 DetectorConstruction, Globals, JsonCpp converters
Valgrind memcheck log attached
Updated by Rogers, Chris about 7 years ago
- #1278 - there was a problem where tracker folks were creating a new instance of the datastructure on every tracker recon step (without deleting it)
- #1293 (item 19) - I list the bits of Geant4 that I couldn't figure out how to clean up. I believe the Geant4 memory leaks are only when the geometry is instantiated i.e. at start of run. I guess this was done against G4.9.2, I haven't checked G4.9.6.