| Summary: | break from the application with optical processes in multi-threading mode | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | Ivana.Hrivnacova |
| Component: | track | Assignee: | asai |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | andrea.dotti |
| Priority: | P5 | ||
| Version: | 10.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Attachments: | tar file with modified macro and gdb outputs | ||
Hello, if bug happens in optical physics then it should be assigned to Peter Gumplinger to category processes/optical VI I suspect this has to do with:
G4Track::CalculateVelocityForOpticalPhoton()
which uses:
groupvel = mat->GetMaterialPropertiesTable()->GetProperty("GROUPVEL");
groupvel->Value(current_momentum);
A race condition issue was identified in G4MaterialPropertyTable class and fixed. |
Created attachment 257 [details] tar file with modified macro and gdb outputs We are getting break in Geant4 VMC test which defines the same setup as the extended OpNovice example when running in multi-threading mode. The break can be reproduced with OpNovice example with modified test macro as attached and changing the verbosity level fVerboseLevel=0 in OpNovicePhysicsList.cc. I attach the GDB back trace from OpNovice example (bt.txt) and also from Geant4 VMC example (bt_vmc.txt). They are a bit different, but both point at the updating the GROUPVEL material properties table in tracking. The test was performed with Geant4 10.00.p01, run with 8 threads.