BramDeCneudt commented on issue #1615: Netty leak detector logs "LEAK: 
ByteBuf.release() was not called before it's garbage-collected" in multiple 
unit test with BufferedChannel in the stack.
URL: https://github.com/apache/bookkeeper/issues/1615#issuecomment-438622192
 
 
   Is this issue still open? I also have the same issue but with an other 
stacktrace:
   
   I'm using the old 0.5.0 version from distributed log, has this been patched 
in the later versions?
   
   `2018-11-14 10:28:00.425 ERROR [,,,] 1756 --- [        DL-io-1] 
io.netty.util.ResourceLeakDetector       : LEAK: ByteBuf.release() was not 
called before it's garbage-collected. See 
http://netty.io/wiki/reference-counted-objects.html for more information.
   Recent access records: 0
   Created at:
        io.netty.util.ResourceLeakDetector.track(ResourceLeakDetector.java:237)
        
io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:331)
        
io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:181)
        
io.netty.buffer.AbstractByteBufAllocator.buffer(AbstractByteBufAllocator.java:117)
        
org.apache.distributedlog.EnvelopedEntryWriter.<init>(EnvelopedEntryWriter.java:83)
        org.apache.distributedlog.Entry.newEntry(Entry.java:52)
        
org.apache.distributedlog.BKLogSegmentWriter.newRecordSetWriter(BKLogSegmentWriter.java:434)
        
org.apache.distributedlog.BKLogSegmentWriter.abortTransmitPacketOnClose(BKLogSegmentWriter.java:554)
        
org.apache.distributedlog.BKLogSegmentWriter.access$200(BKLogSegmentWriter.java:102)
        
org.apache.distributedlog.BKLogSegmentWriter$3.onSuccess(BKLogSegmentWriter.java:524)
        
org.apache.distributedlog.BKLogSegmentWriter$3.onSuccess(BKLogSegmentWriter.java:521)
        
org.apache.distributedlog.common.concurrent.FutureEventListener.accept(FutureEventListener.java:42)
        
org.apache.distributedlog.common.concurrent.FutureEventListener.accept(FutureEventListener.java:26)
        
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760)
        
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736)
        
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
        
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
        
org.apache.distributedlog.BKTransmitPacket.notifyTransmitComplete(BKTransmitPacket.java:54)
        
org.apache.distributedlog.BKLogSegmentWriter.addComplete(BKLogSegmentWriter.java:1172)
        
org.apache.bookkeeper.client.PendingAddOp.submitCallback(PendingAddOp.java:311)
        
org.apache.bookkeeper.client.LedgerHandle.sendAddSuccessCallbacks(LedgerHandle.java:1272)
        
org.apache.bookkeeper.client.PendingAddOp.sendAddSuccessCallbacks(PendingAddOp.java:288)
        
org.apache.bookkeeper.client.PendingAddOp.writeComplete(PendingAddOp.java:283)
        
org.apache.bookkeeper.proto.PerChannelBookieClient$AddCompletion$1.writeComplete(PerChannelBookieClient.java:1890)
        
org.apache.bookkeeper.proto.PerChannelBookieClient.handleAddResponse(PerChannelBookieClient.java:1580)
        
org.apache.bookkeeper.proto.PerChannelBookieClient$15.safeRun(PerChannelBookieClient.java:1378)
        org.apache.bookkeeper.util.SafeRunnable.run(SafeRunnable.java:33)
        java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        java.util.concurrent.FutureTask.run(FutureTask.java:266)
        
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        java.lang.Thread.run(Thread.java:748)`

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to