|Message: Re: Problem with !!!!!!!! Filter: auxiliary points are being memory leaked !!!!!||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Dear all, sorry but in the previous message I have forgot to mention the G4 version. I'm using the G4.9.5.p01. In the mean time I have investigate surfing in the code and I have found that the messages are dispatched by the class G4VCurvedTrajectoryFilter Reading the code documentation I have found these messages: // GimmePoints has not been called (it would have set the // pointer to NULL), therefore nobody has taken charge of the // points and they will never be deleted! G4cout << "!!!!!!!! Filter: auxiliary points are being memory leaked !!!!!" << G4endl; then looking few lines before in the GimmePoints method I found this message: // ParticleChangeForTransport invokes this method (via // PropagatorInField) at every Step, even if the step did not // involve PropagatorInField. Must, therefore, ensure that points // submitted by previous invocations of PIF are not // copied. Therefore the points must be cleared. (Note that the // responsibility for deleting the vector lies with the // SmoothTrajctoryPoint, which is the vector's final destination.) // (jacek 08/11/2002). Then seams to me that this must be some how automatic. Trying to read the documentation and also comparing my code with the various examples I'm not able to find out where is my error. Some one please could help me on solve this issue? Best regards, Filippo