Resource leakage PoC #20
Open
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
seregamorph
force-pushed
the
resource-leakage-detector
branch
from
e115560 to
71d0beb
Compare
seregamorph
force-pushed
the
resource-leakage-detector
branch
from
71d0beb to
55f7762
Compare
seregamorph
force-pushed
the
resource-leakage-detector
branch
from
55f7762 to
63161a7
Compare
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.
Track used resources between integration test execution:
TODO add sensors:
Optionally after each test group that share the same config (and accordingly context) it's possible to opt-in call of
System.gc()via option-Dtestsmartcontext.handleAfterClassGroup.gc=true. Usually it's a bad practice, but for the sake of better heap reports this can give better clarity, so makes sense to use from time to time.