Fix memory leak caused by throwableToSpan #2227
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.
📜 Description
The
Hub
holds on to aWeakHashMap
calledthrowableToSpan
which maps root causes of exceptions toSpan
s. The memory leak was caused by theSpan
holding a strong reference to thethrowable
which contains the root cause that is also used as the key for theWeakHashMap
. This means the value of theWeakHashMap
was causing its own key not to be garbage collected and the memory was never freed.The fix is to weakly hold on to the
Span
so it can be garbage collected and thus also the key can be garbage collected afterwards.💡 Motivation and Context
Fixes #2225
💚 How did you test it?
Manual testing using debugger on a modified sample application, then using
visualvm
to trigger GC manually.📝 Checklist
🔮 Next steps