[
https://issues.apache.org/jira/browse/HBASE-23918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049513#comment-17049513
]
Michael Stack commented on HBASE-23918:
---------------------------------------
I like the word 'growy'.
We have ResourceChecker. It tracks a few resource counts like threads and file
descriptors. It'll thread dump if hangers-on. Does this effort relate? Can they
be tied? Or is it strictly object tracking?
> Track sensitive resources to ensure they are closed and assist devs in
> finding leaks.
> -------------------------------------------------------------------------------------
>
> Key: HBASE-23918
> URL: https://issues.apache.org/jira/browse/HBASE-23918
> Project: HBase
> Issue Type: Improvement
> Reporter: Mark Robert Miller
> Priority: Major
>
> Closing some objects is quite critical. Issues with leaks can be quite
> slippery and nasty and growy. Maintaining close integrity is an embarrassing
> sport for humans.
> In the past, those 3 thoughts led me to start tracking objects in tests to
> alert of leaks. Even with an alert though, the job of tracking down all of
> the leaks just based on what leaked was beyond my skill. If it's beyond even
> one devs skill that is committing, that tends to end up trouble. So I added
> the stack trace for the origin of the object. Things can still get a bit
> tricky to track down in some cases, but now I had the start of a real
> solution to all of the whack-a-mole games I spent too much time playing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
