sPHENIX tracking discussion

[Joe Osborn <osbornjd91 AT gmail.com>]

Hi Chris,

I compiled all of the jenkins reports from the leaks I think have something to do with the tracking - I'll take a look and see what I can dig out.

Joe

On Sun, Sep 4, 2022 at 9:33 AM pinkenburg via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov> wrote:

Hi again,

jenkins keeps on finding memory leaks in our tracking:

https://web.sdcc.bnl.gov/jenkins-sphenix/job/sPHENIX/job/test-default-detector-valgrind-pipeline/1909/valgrindResult/pid=32946/

I had a look at those and the regular handling (creating a hitset and
deleting it in the Reset() of the container) looks okay. The small
number of occurrences of the leaks indicates that this doesn't happen
for every hitset. I suspect there is some cleanup (removal of hitsets)
which isn't done properly. I haven't looked at the removal methods - if
they leave allocated memory behind, but my bet is on one of those

Chris

--
*************************************************************

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

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

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