Fixed possible memory leak in ScheduledThreadPoolExecutor (HystrixTimer.java) #1976
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndreyPoznyak
approved these changes
Jan 10, 2020
abrahamcuenca
approved these changes
Jan 29, 2020
|
Fixes #1998 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Found what seems to be a possible memory leak inside HystrixTimer.java caused by cancel operations called on tasks inside a ScheduledThreadPoolExecutor.
The fix helped us and solved the leakage.
Tasks that were canceled due to timeouts were not removed from the scheduler queues unless setRemoveOnCancelPolicy(true) was called on that scheduler on initialization.