Bug #921
GEANT4/Valgrind output
Start date:
29 February 2012
Due date:
% Done:
0%
Estimated time:
Workflow:
New Issue
Description
Looks like geant4 is not shut down properly. This makes a mess, particularly when trying to spot memory leaks in e.g. test output