Open creatorone1 opened 1 week ago
@creatorone1 Your Reactor Netty version is very old (reactorNettyVersion=1.0.23) and not supported anymore. Please update to a supported version (more info here)
@creatorone1 Your Reactor Netty version is very old (reactorNettyVersion=1.0.23) and not supported anymore. Please update to a supported version (more info here)
thx, which version should i use?
@creatorone1 1.1.22
is the latest one, but I would recommend to update your Spring Boot version as fixes related to memory leaks are also done in Spring Framework
@creatorone1
1.1.22
is the latest one, but I would recommend to update your Spring Boot version as fixes related to memory leaks are also done in Spring Framework
thx, when request or response body is very large(over than 5MB), This memo leak problem more likely happen.
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
when I use spring webflux. discovered a memory leak error related to ByteBuf.release() not being called before it is garbage-collected. The error is traced to the AdvancedLeakAwareByteBuf.writeBytes method, leading to a long chain of method calls involving NettyDataBuffer, AbstractJackson2Encoder, FluxMapFuseable, and many others. The leaked memory is created at PooledByteBufAllocator.newDirectBuffer and results in a large number of write and flush operations in the event loop, ultimately affecting system performance.
Expected Behavior
no leak
Actual Behavior
LEAK: ByteBuf.release() was not called before it's garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for more information.
Steps to Reproduce
sometimes,dont know why and how
Possible Solution
dont known
Your Environment