-
Enhancement
-
Resolution: Won't Do
-
Minor
-
1.4.23.Final
Whenever a XnioByteBufferPool.PooledByteBuffer pool is allocated and the closed, the underlying allocated buffer doesn't clean XNIO's ByteBufferSlicePool's thread local caches are not cleared.
- is blocked by
-
XNIO-317 Introduce API to clean ThreadLocal caches from ByteBufferSlicePool
- Resolved
- is cloned by
-
JBEAP-16364 Clear XnioByteBufferPool.PooledByteBuffer pool when close() to avoid direct memory leaking
- Closed
- is related to
-
JBEAP-14074 (7.2.z) OutOfMemoryError: Direct buffer memory when repeating reload
- Closed
- relates to
-
ENTESB-10090 [[UNDERTOW-1277] Clear XnioByteBufferPool.PooledByteBuffer pool when close() to avoid direct memory leaking] appears to be affecting camel-undertow
- Closed
-
WFCORE-4600 Memory leak caused by ByteBufferSlicePool usage
- Closed