Fix memory leak with CglibAopProxy$ProxyCallbackFilter #28888
Closed
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.
Bug report
Bug report and reason is explained very well here #26266.
In the cglib side, this issue #80 is the consequence of trying to solve
CallbackFilter
leak.As vlsi said
Solution
This solution is to try to reduce the leak by make
advisors
andadvisorChainFactory
WeakReference , so that there should have no chance to leak 'big object'. Think about class created by cglib is also 'leaked', I think that should be acceptable.Another quick solution is to make
AbstractAutoProxyCreator
implementsDisposableBean
, clearCallbackFilter
field in generated class.