Message: URGENT Problem with "G4 kernel has come to Quit state" Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question URGENT Problem with "G4 kernel has come to Quit state" 

Keywords: G4 kernel, Quit state
Forum: Run Management
Date: 30 May, 2008
From: Francisco <Francisco>


I was simulating a big amount of events (over 200 millions photons) and 
the programme crashed sending the following message: 

terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc

I believe I made a mistake allocating memory, because with the
command "top" on linux I could see that the used memory was close to my
RAM memory. But anyway, after three failed attempts to simulate with that 
amount of events, Geant4 seems not to want to simulate anymore in batch 
mode and sends the message:

Graphics systems deleted.
Visualization Manager deleting...
G4 kernel has come to Quit state.

but, it simulates with the visualization mode (of course with less events). I
compiled the source code of the installation again, and it didn't work. If I
want to simulate in batch mode, the program simply stops and send the message.
Why is that happening and how can make Geant4 to forget my memory violation
and continue with the simulation without rancour?

Thank you

Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

 Add Message Add Message
to: "URGENT Problem with "G4 kernel has come to Quit state""

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews

[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]