sPHENIX tracking discussion

[Christof Roland <christof.roland AT cern.ch>]

So far I only have one event that made it through valgrind running everything up to 

the SimpleVtxFinder:

/phenix/u/bogui/data/MacrosFileSize/macros/detectors/sPHENIX/valgrind_sivtx.log

I can try to run a larger sample, but this is quite slow.

Cheers

   Christof

On 8. Feb 2022, at 16:27, Anthony Frawley <afrawley AT fsu.edu> wrote:

Hi Christof,

I looked a bit at the vertexing module yesterday, It would be helpful to know if there is a memory leak, or just a failure to release memory. Is there a Valgrind file we can look at?

Tony

---

From: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov> on behalf of Christof Roland via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Sent: Tuesday, February 8, 2022 10:19 AM
To: Hugo Pereira Da Costa via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Subject: [Sphenix-tracking-l] More memory profiles

 

Hi Everybody, 

as promised yesterday I am sending the slides with the memory profiles. See attchment below. 
After the meeting I found and fixed another memory leak related to the make_unique<TrkrCluster_v3> construct. 
The updated memory profiles are included in the sllides. Some profiles are still running, I will update those when done 
and I'll send around the updated slides. 

The indication sfrom yesterday still hold, we have a small memory leak still somewhere around the CASeeding complex
and probably a slightly bigger one around the vertexing modules.

Cheers

   Christof 

_______________________________________________
sPHENIX-tracking-l mailing list
sPHENIX-tracking-l AT lists.bnl.gov
https://urldefense.com/v3/__https://lists.bnl.gov/mailman/listinfo/sphenix-tracking-l__;!!PhOWcWs!j2enwA9NITjQu1Ttho5Ch1jfdQfUCQHAFFEUyErXguYobwxfej7ox99eQieI2s_L$