Fix memory leak in PandoraTranslator #9084
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a memory leak of about 0.2 Mb/event in the pandora<->CMSSW translator. Plots below are for 0 pileup HGCal, since the leak is for each generator particle I don't think it's proportional to pileup (only have gen particles for the signal event).
@lgray says the check for integer charge is unnecessary so the original daughter particle address can used instead of creating a copy.
@lgray, can you check this PR is okay? As I understand it Pandora needs to be told explicitly about relationships, so the
SetMCParentDaughterRelationship
is still required even though the original particle has a pointer to the daughter, right?Both plots are the memory retained by each module (top 25 only) after event execution, excluding the products they put in the event.
Before:
And after: