TrigFastTrackFinder: fix memory leak
Hello,
It is not possible to change the memory management of the RoiDescriptor constituents after it was created via copy constructor. This is because m_manageConstituents is forced to true here, so we always push_back( new RoiDescriptor( *roi.at(i) ) ). Calling manageConstituents(false) afterwards results in a memory leak (ATR-30983), as memory is no longer released in the RoiDescriptor destructor. In this MR, TrigFastTrackFinder no longer calls manageConstituents(false).
Tagging @sutt .
Adding the urgent label to have this in the next release.
Cheers, Bertrand
Edited by Bertrand Martin Dit Latour