Application Seg Faulting on Triton production

Please fill out the following information to help in answering your question, and also see tips for posting code snippets. If you don’t provide this information it will take more time to help with your problem!

_Geant4 Version:_10.6-p3
_Operating System:_Ubuntu 22.04LTS
_Compiler/Version:_clang-14, g++ (11.4.0), gcc (11.4.0)
_CMake Version:_3.22.1

I’m experiencing an issue whenever I run an application I’ve developed in which protons interact with targets of varying materials. The same issue arises regardless of the target material: the runs are ending prematurely with a seg fault and the following message:

-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : Tracking0013
issued by : G4SteppingManager::InvokeAtRestDoItProcs()
No AtRestDoIt process is active!
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------

This invariably follows the production of a Triton which I can see when I switch on the the verbose mode and monitor the tracking information.

In the past, I’ve been able to navigate around this issue by setting different random seeds and keeping the runs to a minimum size. This is not really possible with the current target material of Beryllium oxide which produces these tritons readily. I really need to find a permanent solution to this problem and I’ve been unable to find this so far.

Hopefully someone on the forum will be able to help.