[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2022-11-22 Thread Yun Gao (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yun Gao updated FLINK-16582:

Fix Version/s: 1.16.1
   1.15.4

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Affects Versions: 1.16.0, 1.17.0, 1.15.3
>Reporter: Yun Gao
>Assignee: Yun Gao
>Priority: Minor
>  Labels: auto-deprioritized-major, auto-unassigned, 
> pull-request-available
> Fix For: 1.17.0, 1.16.1, 1.15.4
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



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


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2022-11-22 Thread Yun Gao (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yun Gao updated FLINK-16582:

Labels: pull-request-available  (was: auto-deprioritized-major 
auto-unassigned pull-request-available)

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Affects Versions: 1.16.0, 1.17.0, 1.15.3
>Reporter: Yun Gao
>Assignee: Yun Gao
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.17.0, 1.16.1, 1.15.4
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



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


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2022-11-11 Thread Fabian Paul (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fabian Paul updated FLINK-16582:

Affects Version/s: 1.15.3
   (was: 1.15.2)

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Affects Versions: 1.16.0, 1.17.0, 1.15.3
>Reporter: Yun Gao
>Priority: Minor
>  Labels: auto-deprioritized-major, auto-unassigned, 
> pull-request-available
> Fix For: 1.17.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



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


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2022-11-07 Thread Matthias Pohl (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthias Pohl updated FLINK-16582:
--
Affects Version/s: 1.15.2
   1.16.0
   1.17.0

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Affects Versions: 1.16.0, 1.17.0, 1.15.2
>Reporter: Yun Gao
>Priority: Minor
>  Labels: auto-deprioritized-major, auto-unassigned, 
> pull-request-available
> Fix For: 1.17.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



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


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2022-09-30 Thread Huang Xingbo (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Huang Xingbo updated FLINK-16582:
-
Fix Version/s: 1.17.0
   (was: 1.16.0)

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Priority: Minor
>  Labels: auto-deprioritized-major, auto-unassigned, 
> pull-request-available
> Fix For: 1.17.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



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


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2022-04-13 Thread Yun Gao (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yun Gao updated FLINK-16582:

Fix Version/s: 1.16.0

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Priority: Minor
>  Labels: auto-deprioritized-major, auto-unassigned, 
> pull-request-available
> Fix For: 1.15.0, 1.16.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2021-09-28 Thread Xintong Song (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xintong Song updated FLINK-16582:
-
Fix Version/s: (was: 1.14.0)
   1.14.1
   1.15.0

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Priority: Minor
>  Labels: auto-deprioritized-major, auto-unassigned, 
> pull-request-available
> Fix For: 1.15.0, 1.14.1
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2021-06-11 Thread Flink Jira Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-16582:
---
  Labels: auto-deprioritized-major auto-unassigned pull-request-available  
(was: auto-unassigned pull-request-available stale-major)
Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so 
it is being deprioritized. If this ticket is actually Major, please raise the 
priority and ask a committer to assign you the issue or revive the public 
discussion.


> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Priority: Minor
>  Labels: auto-deprioritized-major, auto-unassigned, 
> pull-request-available
> Fix For: 1.14.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2021-06-02 Thread Flink Jira Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-16582:
---
Labels: auto-unassigned pull-request-available stale-major  (was: 
auto-unassigned pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Priority: Major
>  Labels: auto-unassigned, pull-request-available, stale-major
> Fix For: 1.14.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2021-04-29 Thread Dawid Wysakowicz (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dawid Wysakowicz updated FLINK-16582:
-
Fix Version/s: (was: 1.13.0)
   1.14.0

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Priority: Major
>  Labels: auto-unassigned, pull-request-available
> Fix For: 1.14.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2021-04-27 Thread Flink Jira Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-16582:
---
Labels: auto-unassigned pull-request-available  (was: 
pull-request-available stale-assigned)

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Assignee: Yun Gao
>Priority: Major
>  Labels: auto-unassigned, pull-request-available
> Fix For: 1.13.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2021-04-16 Thread Flink Jira Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-16582:
---
Labels: pull-request-available stale-assigned  (was: pull-request-available)

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Assignee: Yun Gao
>Priority: Major
>  Labels: pull-request-available, stale-assigned
> Fix For: 1.13.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2020-12-07 Thread Robert Metzger (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Metzger updated FLINK-16582:
---
Fix Version/s: (was: 1.12.0)
   1.13.0

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Assignee: Yun Gao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.13.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2020-12-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-16582:
---
Labels: pull-request-available  (was: )

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Assignee: Yun Gao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.12.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-16582) NettyBufferPoolTest may have warns on NettyBuffer leak

2020-03-25 Thread Zhijiang (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhijiang updated FLINK-16582:
-
Fix Version/s: 1.11.0

> NettyBufferPoolTest may have warns on NettyBuffer leak 
> ---
>
> Key: FLINK-16582
> URL: https://issues.apache.org/jira/browse/FLINK-16582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Network, Tests
>Reporter: Yun Gao
>Assignee: Yun Gao
>Priority: Major
> Fix For: 1.11.0
>
>
> {code:java}
> 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
> {code}
> We should released the allocated buffers in the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)