Skip to content

PARTIALLY FIXED: Memory leak

EDIT: 2022-06-07, after applying the patch to FairRoot, the memory growth rate is about 4-6x slower. This is currently manageable.
It seems that the rest of the leak is somewhere in our reconstruction code (some of the memory is not freed after exiting the event), which will be refactored anyway

EDIT: @geraks reported his findings to FairRoot, FairRoot devs acknowledged their fault, and added the fix request to the v19.0 milestone.
https://github.com/FairRootGroup/FairRoot/issues/1075
The fix is already merged into their dev branch
https://github.com/FairRootGroup/FairRoot/pull/1097

So, this bug is planned to be removed in v19.0 release of FairRoot.  
The date of release is not set yet.

Huge memory leak in current dev branch

AuAu sqrt(s)=11.5 is requested 6GB

***  Event # 818
=====   MpdTpcKalmanFilter   =====
MpdTpcKalmanFilter::Reset
User CPU time: 76805.9 Memory: resident 6028436, virtual 6285280
Edited by Slavomir Hnatic
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information