cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13906) Properly close StreamCompressionInputStream to release any ByteBuf
Date Fri, 29 Sep 2017 22:25:00 GMT


Jason Brown commented on CASSANDRA-13906:

bq. Isn't that kind of abusing the idiom of reference counting by not counting?

That is true to a degree, but I'm never sure if any code would, in some broken way, become
executed twice and fail on the refCnt decrement and mask some other problem. I could set the
buffer to null after a simple call to {{release()}}. wdyt?

> Properly close StreamCompressionInputStream to release any ByteBuf
> ------------------------------------------------------------------
>                 Key: CASSANDRA-13906
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jason Brown
>            Assignee: Jason Brown
> When running dtests for trunk (4.x) that perform some streaming, sometimes a {{ByteBuf}}
is not released properly, and we get this error in the logs (causing the dtest to fail):
> {code}
> ERROR [MessagingService-NettyOutbound-Thread-4-2] 2017-09-26 13:42:37,940
- LEAK: ByteBuf.release() was not called before it's garbage-collected. Enable advanced leak
reporting to find out where the leak occurred. To enable advanced leak reporting, specify
the JVM option '-Dio.netty.leakDetection.level=advanced' or call ResourceLeakDetector.setLevel()
See for more information.
> {code}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message