Problem 884 - Apparent memory leak in G4ParaFissionModel
Summary: Apparent memory leak in G4ParaFissionModel
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/hadronic/models (show other problems)
Version: 8.1
Hardware: Other Other
: P2 normal
Assignee: dennis.herbert.wright
URL:
Depends on:
Blocks:
 
Reported: 2006-08-22 18:08 CEST by dale.prokopovich
Modified: 2007-01-05 17:26 CET (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description dale.prokopovich 2006-08-22 18:08:26 CEST
I would like to report a problem I think I have found where G4ParaFissionModel
is eating memory. I think the problem occurs in the production of the fission
products so that the more fissions that occur the more memory that is eaten. I
do not need a thick film of material in my simulation however I do need a huge
number of primary neutrons in the simulation so I still have a problem with the
memory being allocated an not released.

I may have located the source of the leak to the allocation of a new
G4DynamicParticle for the secondaries which appears to go out of scope and if
not released after being passed back to theResult.push_back()

I can provide a basic example simulation if needed.

I am running GEANT4.8.1.p01 with Fedora Core 4 and gcc 4.0.0 20050519 (RedHat
4.0.0-8)

Thanks and Best Regards,
Dale.

P.S. Has the problem with the neutron Inelastic process only selecting the
natural isotopic abundance of the isotopes in the materials regrdless of their
defined isotopic composition been rectified or is there a workaround?
Comment 1 dennis.herbert.wright 2006-09-01 11:45:59 CEST
Thanks for the report.  Please send your example code to me at
dwright@slac.stanford.edu

We are now working on the isotope choice problem, but as it involves changes at a
rather basic level, a lot of code is affected.  We expect to have it fixed before
the December release, but most likely sooner.
Comment 2 dennis.herbert.wright 2007-01-05 17:26:59 CET
Memory leaks found and fixed.