You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/07/02 11:42:04 UTC

[jira] [Updated] (CASSANDRA-9423) Improve Leak Detection to cover strong reference leaks

     [ https://issues.apache.org/jira/browse/CASSANDRA-9423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict updated CASSANDRA-9423:
--------------------------------
    Fix Version/s:     (was: 2.1.8)
                   2.2.0 rc2

> Improve Leak Detection to cover strong reference leaks
> ------------------------------------------------------
>
>                 Key: CASSANDRA-9423
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9423
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>             Fix For: 3.0.0 rc1
>
>
> Currently we detect resources that we don't cleanup that become unreachable. We could also detect references that appear to have leaked without becoming unreachable, by periodically scanning the set of extant refs, and checking if they are reachable via their normal means (if any); if their lifetime is unexpectedly long this likely indicates a problem, and we can log a warning/error.
> Assigning to myself to not forget it, since this may well help especially with [~tjake]'s concerns highlighted on 8099 for 3.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)