-
Notifications
You must be signed in to change notification settings - Fork 962
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
Memory Leak observed after enabling Redis cache #1163
Comments
The allocation and Lettuce isn't using |
I took this opportunity to add |
Hi @mp911de, thanks for adding The reason I believe that this is related to Lettuce is that it occurs in the thread named: |
May I close this ticket or is there anything else I can assist you with? |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Hi,
I recently started using lettuce client for Redis and after that I have been observing memory leak issue in my application, as reported by Netty's memory leak detector.
I added the following configuration to capture the source of memory leak:
-Dio.netty.leakDetection.level=advanced -Dio.netty.leakDetection.targetRecords=50
Even after adding this configuration, I only get part of the stack trace. The following call trace is from the thread named:
lettuce-nioEventLoop-6-12
I was hoping this ByteBuf to be further handled by
io.lettuce.core.protocol.CommandHandler
and released but somehow that is missing.Any help in debugging this will be really useful.
The text was updated successfully, but these errors were encountered: