|Message: Re: Memory leak in QGSP?||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 Thu, 20 Jul 2006, Huaimin Liu wrote: > *** Discussion title: Hadronic Processes > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/hadronprocess/540"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Dear Geant4 experts, > > When I run the advanced example lAr_calorimeter using 500 MeV pi-, > the memory increases with the event number (lets say 200000). The > hadronic package QGSP is used in this example. We also observed > the leakage in our own application if QGSP was used. We are using > Geant4.8.1, but it is the same with other previous Geant4 releases. > Any ideas? > > Huaimin Liu > IHEP, Beijing > Hello, During testing of G4 8.1 such leak was not observed. A simple test may be if you substitute QGSP by LHEP Physics List - is leak there or not? If will not disappear, likely problem is inside your application. Another possibility is a non-standard computing platform (OS, compiler, CLHEP...) - if it very different from our "official" variant, which were well tested. VI
|Inline Depth:||Outline Depth:||Add message:|