| Summary: | Memory Leak in G4NuclearDecay | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | d.kruecker |
| Component: | processes/hadronic/models | Assignee: | flei |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 6.2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
Sorry, I truncated the file name. The correct name is G4NuclearDecayChannel.cc Dirk Kruecker thank you Dirk, we'll correct it. Fixed in tag 'geant4-07-00-ref-02' |
There is a memory leak in G4NuclearDecay::DecayIt() if the daughter nucleus is in an excitate state. This can be observed in e.g. examples/extended/radioactivedecay/exrdm/ if the ion in the exrdm.in is replace by an isotop where the daughter nucleus emitts gammas, e.g Y86 (/gps/ion 39 86). The job increases by about 12MB/100K events. The problem seems to be at (Geant4.7.0/4.6.2) G4NuclearDecay.cc line 459: dynamicDaughter = new G4DynamicParticle (theIonTable->GetIon(daughterZ,daughterA,finalDaughterExcitation), daughterMomentum1); There should be a delete dynamicDaughter; before the pointer is reused. Best regards, Dirk Kruecker