sPHENIX tracking discussion

[pinkenburg <pinkenburg AT bnl.gov>]

    Hi Christof,
    
    the event is cleared in a separate step - after processing by
    calling the Reset() method for every object under the DST node (we
    have some opaque foreach type way to iterate over the node tree,
    what is being executed here is
    offline/framework/phool/PHNodeReset.cc).
    
    I think the problem is likely in a Reset() method of the container.
    Which one we are talking about is opaque to me but if I look at the
    containers in trackbase, they just clear their map without calling
    the Reset() method of their members. If a member of this map
    allocates memory it leaks right there.
    
    Chris

On 1/20/2022 7:49 AM, Christof Roland via sPHENIX-tracking-l wrote:

      Hi Everybody,

I tried a few stunts to find the memory leak in the TpcClusterizer and what finally 

stopped it was turning off the creation of the ClusterHitAssoociation map. 

With this disabled the memory along 1000 events is pretty stable. See PrMon plot below.

It looks like thes ClusterHitsAssoc map is not properly reset. Looking in the Clusterizer code 

neither the clustermap nor the assoc map are reset. Which makes sense since the INTT and 

MVTX clusterizers also write to the same maps. 

While ClusterMap apparently gets reset properly, the assoc map doesn't.

Where do we do this actually?

Cheers

   Christof 

_______________________________________________
sPHENIX-tracking-l mailing list
sPHENIX-tracking-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/sphenix-tracking-l
    
    
-- 
*************************************************************

Christopher H. Pinkenburg	;    pinkenburg AT bnl.gov
				;    http://www.phenix.bnl.gov/~pinkenbu

Brookhaven National Laboratory	;    phone: (631) 344-5692
Physics Department Bldg 510 C	;    fax:   (631) 344-3253
Upton, NY 11973-5000

*************************************************************