|Message: Re: Geant4 eating up memory!||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
On Wed, 6 Jul 2005, Zach Hartwig wrote: > *** Discussion title: Run Management > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/runmanage/104"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Hi everyone, > > I'm currently having a nasty problem with Geant4 and memory. > During run-time, Geant4 rapidly consumes memory. If a sufficient > number of events are generated (~100), Geant4 eventually eats up > all the available memory and freezes the computer. > > A simple description: I have a circular "storage" tube composed > of 12 identical "G4Tubs" sections of 30 degrees each composed > of vacuum. There are 1cm thick aluminum walls that surround each > of the 12 vacuum sections, each of the 4 walls (top,bottom,2 sides) > are also "G4Tubs" of 30 degrees each. A magnetic field, that I have > derived from G4MagneticField, is placed within the regions surrounded > by the aluminum walls. > > Things I have tried to eliminate memory issues: > -eliminated all optional user classes(ie, eventAction, steppingAction...) > -ran the geant4 geometry tests and got no overlapping, no spurious errors > -stripped down my complicated geometry to the one described above > -turned off trajectory storage > -ran Geant4 with memory checker "valgrind" > -ensured all created objects are deleted > > Any suggestions on where to find these mysterious and devastating memory > leaks would be greatly appreciated! Thanks very much. > > ~Zach > > Please, run any of G4 official example. If you will have the same leak, it will be an indication of problem of installation, if no - problem in your application. VI
|Inline Depth:||Outline Depth:||Add message:|