-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b104
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8156401 | 8u111 | Tony Printezis | P4 | Resolved | Fixed | b01 |
| JDK-8153975 | 8u102 | Christoph Langer | P4 | Resolved | Fixed | b03 |
| JDK-8162236 | emb-8u111 | Tony Printezis | P4 | Resolved | Fixed | b01 |
Some NIO channel operations use temporary DirectByteBuffers which are cached in thread-local caches to avoid having to allocate / free a buffer at every operation.
Unfortunately, there is no bound imposed on the size of buffers added to the thread-local caches. So, infrequent channel operations that require a very large buffer can create a native memory leak.
We should introduce a property, jdk.nio.MaxCachedBufferSize that if set sets a limit on the size of the buffers that can be added to the thread-local caches. Operations that require a buffer that is larger than this limit will allocate then free an one-off buffer.
Unfortunately, there is no bound imposed on the size of buffers added to the thread-local caches. So, infrequent channel operations that require a very large buffer can create a native memory leak.
We should introduce a property, jdk.nio.MaxCachedBufferSize that if set sets a limit on the size of the buffers that can be added to the thread-local caches. Operations that require a buffer that is larger than this limit will allocate then free an one-off buffer.
- backported by
-
JDK-8153975 (bf) Allow users to bound the size of buffers cached in the per-thread buffer caches
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- csr of
-
CCC-8147468 (bf) Allow users to bound the size of buffers cached in the per-thread buffer caches
-
- Closed
-
- relates to
-
JDK-8148540 sun/nio/ch/TestMaxCachedBufferSize.java fails on 32bit system
-
- Open
-
There are no Sub-Tasks for this issue.