DecayTreeFitterAlg leaks memory
Running a series of DecayTreeFitterAlgs
over about 15k events can double the memory use from about 3.3GB to > 7GB. Disabling these makes the memory still increase, but only a bit (so there's some chance there are more memory leaks out there).
It's important to have this fixed not only for tupling, but also for HLT2. My suspicion is that the relateTree
function is responsible, as already cloned particles get cloned again.