[jira] [Commented] (CASSANDRA-19783) In-jvm dtest to detect InstanceClassLoaderLeaks

["Doug Rohrer (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-19783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867092#comment-17867092 ] 

Doug Rohrer commented on CASSANDRA-19783:
-----------------------------------------

*In-jvm dtest API PR:*

[https://github.com/apache/cassandra-in-jvm-dtest-api/pull/39]

*Cassandra Trunk PR:*

[https://github.com/apache/cassandra/pull/3429]

> In-jvm dtest to detect InstanceClassLoaderLeaks
> -----------------------------------------------
>
>                 Key: CASSANDRA-19783
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19783
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Test/dtest/java
>            Reporter: Doug Rohrer
>            Priority: Normal
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> It is currently very easy to add dependencies/code that cause in-jvm dtest {{InstanceClassLoader}} leaks, and hard to find them. These patches add a WeakHashSet that allows us to count the number of reachable InstanceClassLoaders in the in-jvm dtest API, so that we can use it in the ResourceLeakTest in the actual Cassandra branches in CI (it only takes 2 iterations to find the leak recently introduced by the inclusion of the {{oshi.jna }}library, which was fixed in [https://github.com/apache/cassandra-in-jvm-dtest-api/pull/38])



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org