Automatically clean up leaked openslide_t
/openslide_cache_t
refs
#77
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.
Call
openslide_close()
/openslide_cache_release()
from aCleaner
, ensuring we don't leak a handle ifOpenSlide.close()
/OpenSlideCache.close()
is not called. Move the handle into a separateWrapper
class; we can't implement the cleanupRunnable
directly onRef
because then theCleaner
would keep theRef
alive.The
OpenSlide.close()
/OpenSlideCache.close()
methods are still the preferred way to release an object, since they're explicit and eager.