[java] timely get rid of the SelectorManager threads #11283
Closed
Conversation
This file contains hidden or 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
In cases where a lot of WebDrivers are created, timely closed and there is no GC done, a lot of SelectorManager threads are running. Calling the GC explicit is not best practice, but it is the only way to stop these threads.
|
SonarCloud Quality Gate failed. |
|
The approach suggested here is not ideal since it manually calls GC. Closing in favor of #11345 which helps fix the same issue. |
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.
Description
In cases where a lot of WebDrivers are created, timely closed and there is no GC done, a lot of SelectorManager threads are running. Calling the GC explicit is not best practice, but it is the only way to stop these threads.
Has been reported in #11270
Types of changes
Checklist