You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use spring webflux and lettuce. When I want to set the lettuce worker thread not on the io thread, my service will find that the memory surges every once in a while, and the service will become unresponsive and stuck after a while.
one instance of io.netty.channel.socket.nio.NioSocketChannel loaded by org.springframework.boot.loader.LaunchedURLClassLoader @ 0x6458005b0 occupies 2,443,638,760 (91.93%) bytes. The memory is accumulated in one instance of java.lang.Object[], loaded by <system class loader>, which occupies 2,443,636,752 (91.93%) bytes.
Thread io.netty.util.concurrent.FastThreadLocalThread @ 0x645bb4888 lettuce-nioEventLoop-7-1 has a local variable or reference to sun.nio.ch.EPollSelectorImpl @ 0x645bbe688 which is on the shortest path to java.lang.Object[550104] @ 0x6e43aa798. The thread io.netty.util.concurrent.FastThreadLocalThread @ 0x645bb4888 lettuce-nioEventLoop-7-1 keeps local variables with total size 29,232 (0.00%) bytes.
Significant stack frames and local variables
sun.nio.ch.EPollSelectorImpl.doSelect(Ljava/util/function/Consumer;J)I (EPollSelectorImpl.java:118)
sun.nio.ch.EPollSelectorImpl @ 0x645bbe688 retains 832 (0.00%) bytes
sun.nio.ch.SelectorImpl.lockAndDoSelect(Ljava/util/function/Consumer;J)I (SelectorImpl.java:129)
sun.nio.ch.EPollSelectorImpl @ 0x645bbe688 retains 832 (0.00%) bytes
The text was updated successfully, but these errors were encountered:
thanks for reporting this issue. Could you help us reproduce this so we can solve it?
Can you build up a minimum reproducible example that showcases the issue, or is it very random?
How often does it happen?
Uh oh!
There was an error while loading. Please reload this page.
Bug Report
Current Behavior
I use spring webflux and lettuce. When I want to set the lettuce worker thread not on the io thread, my service will find that the memory surges every once in a while, and the service will become unresponsive and stuck after a while.
Stack trace
Input Code
Input Code
Old configuration mode, no memory leak occursNew configuration mode, will trigger memory leak occurs
Expected behavior/code
Environment
Possible Solution
Additional context
memory dump
The text was updated successfully, but these errors were encountered: