-
Notifications
You must be signed in to change notification settings - Fork 177
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
ResourceLeakDetector reporting "LEAK: ByteBuf.release() was not called before it's garbage-collected" #248
Comments
If you would like us to spend some time helping you to diagnose the problem, please spend some time describing it and, ideally, providing a minimal sample that reproduces the problem. The actual usage can be cruical for reproducing the issue. Please ideally use R2DBC SPI only without any 3rd-party libraries to provide a reproducer. |
Along with efforts around #245, we closed a memory leak that was releated to closing the client. You might want to upgrade to the latest snapshots and retest. |
I just finished building a simple reproducer that does it 99% of the time. Will test that snapshot today and be back with whether or not it fixes that issue ! |
We did update to the latest snapshot (0.8.2-SNAPSHOT) but we ended up with a new error blocking the service entirely. This error does not happens when we use the 0.8.0-RELEASE (maybe this is linked to another change in the SNAPSHOT?) What we found is that our application is blocked by a thread after a cancel and end up using 100% of the CPU. Here is what we found in VisualVM: And here is what the thread is blocked on : And monitoring postgresql with pg_activity, we found that multiple queries were in This seems to happen when the service is under heavy load and start to timeout request. I'll try to provide a minimal sample that can reproduce this error asap but in the meantime I wanted to report issue we have with the last snapshot. |
We fixed the infinite loop issue with #242. I wouldn't be surprised if there's another issue that causes the infinite loop as we entirely rewrote command queueing between 0.8.0 and 0.8.1. |
Closing due to inactivity. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Bug Report
It seems that netty's ResourceLeakDetector is complaining about memory leak issues as per
LEAK: ByteBuf.release() was not called before it's garbage-collected
Versions
Current Behavior
During operation, Netty is complaining about leaks which I can't diagnose myself.
Table schema
table is a simple key(string)/value(json) table with primary key... on the key table
Steps to reproduce
Actually using simple Spring R2DBC findById method
Expected behavior/code
No warnings in the code
Possible Solution
Nope :(
Additional context
N/A
The text was updated successfully, but these errors were encountered: