Message: Re: Geant eating memory Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: Geant eating memory 

Forum: Run Management
Re: Question Geant eating memory (Christian Doerr)
Date: 10 May, 2002
From: Vladimir Ivanchenko <Vladimir Ivanchenko>

On Fri, 10 May 2002, Christian Doerr wrote:

> *** Discussion title: Run Management
> Email replies to must include:
>   In-Reply-To: <"/runmanage/7">
>   Subject: ...change this to be about your reply.
> Hello everybody,
> I hope this is the right category for my question, but I think
> my problem has to do with it.

Hello Christian,

Memory leak is as rule not easy problem to debug, so I cannot give you
complete answer what to do, but I propose to exclude some moments.

> I'm running a simulation of radioactive decays in an underground
> setup, means I need to simulate a lot of decays for a lot 
> of nuclides, i.e. in the order of 10^8 events per run.
> My problem currently is that my program works fine except for
> the fact that the process is getting bigger and bigger and after
> 8 million or so events all of my 256 MB memory are full and 
> the system crashes.
> In the programm the recording is done by my own Recorder class,
> which writes all results to a ROOT file, so I don't want 
> geant4 to keep any kind of information concerning hits, tracks, 
> steps, etc. in memory after the event is processed and the next
> decay is ready to start. I also observed that after the end of 
> a run the process size doesn't change, also after closing 
> the ROOT output files

G4 does not keep any information unless user application is doing that. If
leak is in G4 it should be fixed.

> How can I find out where geant4 is eating all my memory?
> What kind of information does geant4 keep in memory during a run?
> Is there anything like 
> aRun->RemoveEveryUnnecessaryInformationFromMemory(); ?
> :)
> Thanks a lot for any suggestions.
> Christian
> PS: I'm using Root version 3.01/06 and Geant4 4.0
>     under SuSE Linux 7.3 with gcc version 2.95.3

I would suggest:

1. To use Geant4 4.0.p02 -> 4.0 is not recommnded
2. As a test, remove access to ROOT and reproduce a leak
3. Than additionly remove all user actions and reproduce a leak
4. After that it will be clear that leak is in G4 and you can, for
example, submit a G4 bug report, or post in hypernews two things:
primary generator + physics list.

cheers, VI

Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

 Add Message Add Message
to: "Re: Geant eating memory"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews

[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]