Project

General

Profile

Bug #1955

MAUS memory usage

Added by Rajaram, Durga over 5 years ago. Updated over 5 years ago.

Status:
Open
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11 February 2018
Due date:
% Done:

0%

Estimated time:
Workflow:
New Issue

Description

Logging seemingly increased memory usage running globals.

Files

valgrind-trunk-r1259.log (9.83 MB) valgrind-trunk-r1259.log Rajaram, Durga, 11 February 2018 20:58
valgrind-definitely-lost.log (4.28 MB) valgrind-definitely-lost.log Rajaram, Durga, 12 February 2018 08:30
#1

Updated by Rajaram, Durga over 5 years ago

There are a couple of puzzling (to me) messages from TrackMatching->DSTrack->FixTrackerTime, and AddVirtualTrackPoints -- think those get deleted by the primary chain destructor and/or ultimately by the global event destructor.

Also a lot of Geant GDMLRead errors -- tried slac geant forums in vain. And a bunch from MiceModules, ModuleTextFileIO.
Wondering if those geant and micemodule leaks show up more with globals because of the repeated geometry lookups...

#2

Updated by Rajaram, Durga over 5 years ago

Valgrind log added -- with line numbers! -- against a random run 10082, run with globals.

#3

Updated by Rajaram, Durga over 5 years ago

added log of just the "definitely lost" records
mostly GEANT + MiceModule + OutputCppRoot + a few globaltrackmatching and emr

Also available in: Atom PDF