-
**BUG REPORT**
***Describe the bug***
While testing BufferedChannel's read instance method (with buf capacity=100B, wrote data through the buffered channel=300B),
it happens that when the read…
-
### Bug Description
We have a Spring Cloud Gateway Application which uses Netty as a server to process request/response. We see a spike of IllegalReferenceCountException happening on a particular TCP…
-
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
## Y…
-
**Basic details**
- **Are you using a legitimate Minecraft account?**: yes
- **Are you using Java 8, 64-bit?**: yes
- **Did you add any additional mods**: no
- **Crash/latest log link (if appl…
-
19:03:19.127 [LittleProxy-0-ProxyToServerWorker-4] ERROR io.netty.util.ResourceLeakDetector - LEAK: ByteBuf.release() was not called before it's garbage-collected. See http://netty.io/wiki/reference-c…
-
-
In order to improve serialization/deserialization performance, it would be nice to have support for netty's [ByteBuf](http://netty.io/4.0/api/io/netty/buffer/ByteBuf.html).
Current protostuff API des…
-
Currently the adaptive pool is splitting the allocation by:
- creating/reusing an "empty" `AdaptiveByteBuf`, at https://github.com/netty/netty/blob/c0fdb8e9f8f256990e902fcfffbbe10754d0f3dd/buffer/src…
-
### Describe the bug
An application that relies on S3AsyncClient is intermittently experiencing the error below.
```
LEAK: ByteBuf.release() was not called before it's garbage-collected. See http…
-
Neo4j db pod crashed and was not able to recover back automatically
## Example bug report
```
2024-07-18 06:13:51.508+0000 ERROR LEAK: ByteBuf.release() was not called before it's garbage-colle…