-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 #3881
Comments
tried also with |
@Dambldore is this anyhow connected to the comment in #3541 (comment) ? |
no this is another issue with the same problem with buffer leak. |
@Dambldore thanks. I see. I am not sure whether this is the right repository to report this. From the logs you provided, the only hints of reactor.core are
and these areas seem unlikely to cause a leak. I'm not saying they are not responsible, but without a reproducible example it's not feasible to work with this. And the scope is rather broad - you mention a migration from Boot 2.7 (!) to 3.3. I'd suggest minimizing the scope as much as possible on your end first. Regarding a migration to Boot 3.3, the regular path is to go gradually between minors (2.7 -> last 2.7 patch; 2.7 -> 3.0 -> 3.1 -> 3.2 -> 3.3). Here are some ideas:
With a specific set of dependencies and a reproducible example we can try to suggest which project might be at fault for the particular team to have a look. |
After migrating from spring boot 2 (2.7.13) to spring boot 3 (3.3.2)
Expected Behavior
No memory leak
Actual Behavior
Memory leak after 1-3 hours after intense load in production
Your Environment
JVM:
openjdk version "17.0.2" 2022-01-18
kotlin: 1.9.24
OS:
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
5.15.0-116-generic
My log:
The text was updated successfully, but these errors were encountered: