attempt to fix thread mis-killing, which happens with memory monitor. #118
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
|
Thank you for this contribution! |
|
Struggeling at the moment to deploy to Maven Central (since Bintray shut down) - should hopefully have sorted that out soon, just waiting for the ticket https://issues.sonatype.org/browse/OSSRH-73369 |
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.
I use this sandbox in production, and found it incorrectly killed some execution,and found the reason was on the 'getThreadAllocatedBytes' method.
so I change the count method to avoid this, and this solution works.
it might loose the accuracy of memory limit, the maintainer must consider this, it's a tricky problem.