Message: Re: Geant eating memory Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: Geant eating memory 

Forum: Run Management
Re: Question Geant eating memory (Christian Doerr)
Date: 16 May, 2002
From: Makoto Asai <Makoto Asai>


 I would suggest you to check whether you have unnecessary
"hard-coded" UI commands. For example, which is one of the
most typical user's mistake, don't you use UI command instead 
of directly invoking the proper set-method for changing the 
direction of primary particles generated by G4ParticleGun? 

 In current implementation, G4UImanager keeps all UI commands
as history. Thus if your code has G4UImanager::ApplyCommand()
method within event loop, the size of your program is getting
begger as the number of processed event. This is not a memory
leak. All stored history will be deleted at the end of program.
In the next public release, G4UImanager will have a limit for
the number of stored history. Thus you will not see any memory
exhaust by UI commands.

 On the other hand, UI command should not be used for this 
kind of "frequent" and "massively used" setting. It is mush 
slower compared to direct method invokation.

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

 Add Message Add Message
to: "Re: Geant eating memory"

 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 ]