fix(fd): close leaked file descriptors #1445
Merged
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.
Welcome to Cryostat! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
git commit --amend --signoff
Fixes: #1444
Depends on cryostatio/cryostat-core#207 (these changes are really separate, but I want to update
-core
and include that dependency update in this same PR for simplicity)Description of the change:
This simply closes some file descriptors that are currently leaked.
Motivation for the change:
Don't leak resources over time.
How to manually test:
See test procedure in cryostatio/cryostat-core#207 . Same thing applies.
ls -l /proc/$pid/fd
is useful for checking which descriptors look like they've been leaked. I used the following to ease tracing where those descriptors got opened:https://github.com/jenkinsci/lib-file-leak-detector downloaded and placed into my
cryostat/clientlib
project directory, named asfile-leak-detector.jar
.