Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-16582

NettyBufferPoolTest may have warns on NettyBuffer leak

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      4749 [Flink Netty Client (50072) Thread 0] ERROR
      org.apache.flink.shaded.netty4.io.netty.util.ResourceLeakDetector [] - LEAK:
      ByteBuf.release() was not called before it's garbage-collected. See
      https://netty.io/wiki/reference-counted-objects.html for more information.
      Recent access records: 
      Created at:
      	org.apache.flink.shaded.netty4.io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:349)
      	org.apache.flink.shaded.netty4.io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:187)
      	org.apache.flink.shaded.netty4.io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:178)
      	org.apache.flink.shaded.netty4.io.netty.buffer.AbstractByteBufAllocator.buffer(AbstractByteBufAllocator.java:115)
      	org.apache.flink.runtime.io.network.netty.NettyBufferPoolTest.testNoHeapAllocations(NettyBufferPoolTest.java:38)
      	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	java.lang.reflect.Method.invoke(Method.java:498)
      	org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
      	org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
      	org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
      	org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
      	org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
      	org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
      	org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
      	org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
      	org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
      	org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
      	org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
      	org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
      	org.junit.runners.ParentRunner.run(ParentRunner.java:363)
      	org.junit.runners.Suite.runChild(Suite.java:128)
      	org.junit.runners.Suite.runChild(Suite.java:27)
      	org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
      	org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
      	org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
      	org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
      	org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
      	org.junit.runners.ParentRunner.run(ParentRunner.java:363)
      	org.junit.runner.JUnitCore.run(JUnitCore.java:137)
      	com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
      	com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:33)
      	com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:230)
      	com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:58)
      
      
      Test ignored.
      
      
      Process finished with exit code 0
      

      We should released the allocated buffers in the tests.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            gaoyunhaii Yun Gao
            gaoyunhaii Yun Gao
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment