[RF] Do not stream RooAbsArg eocache to avoid memory leak when reading back workspaces #12024
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 memory leak is demonstrated with the following ROOT macro:
along with a modification to
RooExpensiveObjectCache
to printout when an instance is being constructed or destructed. Before this fix the above then prints out (I annotated the output a bit):After the fix caches are created and destroyed as expected: