-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LEAK: ByteBuf.release() was not called before it's garbage-collected #9350
Comments
@Umang-Goel from the log it seems like your |
@normanmaurer We are not explicitly using
Do you have any idea which of these might be using the NettyServerHandler? Also, is there any way that we can explicitly use io.netty.util.ReferenceCountUtil.release() to fix the issue? |
@Umang-Goel then open a GRPC issue... /cc @carl-mastrangelo @ejona86 |
Yeah, please open an issue on grpc/grpc-java repository. You can reference this one. There are some ways for interceptors to cause this and there's also the bug grpc/grpc-java#5576 that could trigger this as well. There will need to be some back-and-forth to figure out where the issue is. |
Thanks all for your input. As suggested, I've opened the issue on grpc/grpc-java |
@Umang-Goel can you just add a reference to the issue here so we can close this one ? |
Sure, I've updated the comment. |
Expected behavior
No leak
Actual behavior
Steps to reproduce
It is happening randomly.
Flags used to launch jvm:
-Xmx256m
-XX:MaxDirectMemorySize=256m
We are also getting below logs:
Minimal yet complete reproducer code (or URL to code)
Netty version
JVM version (e.g.
java -version
)Java(TM) SE Runtime Environment (build 8.0.5.26 - pap6480sr5fp26-20181115_03(SR5 FP26)) IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed References 20181106_401576 (JIT enabled, AOT enabled) OpenJ9 - fde1d6f OMR - d8c3617 IBM - 5c4a9f0) JCL - 20181022_01 based on Oracle jdk8u191-b26
OS version (e.g.
uname -a
)I got the above log by setting
-Dio.netty.leakDetection.level=paranoid
.The text was updated successfully, but these errors were encountered: