cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9656) Strong circular-reference leaks
Date Mon, 06 Jul 2015 10:43:04 GMT


Benedict commented on CASSANDRA-9656:

Good catch on {{testSSTableSplit}}, though this was true in 2.1 also. I'll commit with that

{{testFileRemoval}}: can't see this in the prior version. Are you referring to {{testNumberOfFiles_truncate}}?
That one was deliberate, since the truncate should be a no-op there, as we already confirm
the directory is empty, and validate our internal contents are equivalent to that empty directory.

> Strong circular-reference leaks
> -------------------------------
>                 Key: CASSANDRA-9656
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Critical
>             Fix For: 2.1.8
> As discussed in CASSANDRA-9423, we are leaking references to the ref-counted object into
the Ref.Tidy, so that they remain strongly reachable, significantly limiting the value of
the leak detection.

This message was sent by Atlassian JIRA

View raw message