Project

General

Profile

Bug #566

Memory leak?

Added by Santos, Edward over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Simulation
Target version:
Start date:
11 July 2011
Due date:
% Done:

100%

Estimated time:
Workflow:

Description

Not sure this is a memory leak, but i have my doubts that this is an intentional feature.

All the observations that follow refer to code freshly pulled from the trunk.

When running the simulation (without any digitization), the json output file gets a new line for each spill we run. The number of hits in the "mc" branch of each new line grows with each new spill. Shouldn't there be a reset? If we try to run a large number of events, the memory consumption becomes unbearable at some point. (Had to restart my laptop when trying to run 1000 spills).

ES


Related issues

Blocked by MAUS - Feature #567: SpecialVirtual detectorsClosedRogers, Chris11 July 2011

Actions
#1

Updated by Tunnell, Christopher over 10 years ago

  • Tracker changed from Feature to Bug

Are you using the trunk version? I think this is an old bug:

bzr pull lp:maus

or

bzr merge lp:maus

#2

Updated by Santos, Edward over 10 years ago

Yes, I'm using the trunk version.

I first found this feature on my own version and then verified it in code just pulled from the trunk.

#3

Updated by Tunnell, Christopher over 10 years ago

ClearSDHits() within MICEDetectorConstruction isn't being called anymore...

#4

Updated by Rogers, Chris over 10 years ago

  • Target version set to Future MAUS release

Ack - sorry... not in a test so I broke it when I updated the code. Will implement fix plus test ASAP.

#5

Updated by Rogers, Chris over 10 years ago

Fixed and tested in rogers

#6

Updated by Rogers, Chris over 10 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

r581

#7

Updated by Rogers, Chris over 10 years ago

  • Target version changed from Future MAUS release to MAUS-v0.0.4

Also available in: Atom PDF