Details
-
Bug
-
Resolution: Fixed
-
P3
-
11, 12, 13
-
b23
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8232212 | 11.0.6-oracle | Thomas Stuefe | P3 | Resolved | Fixed | b01 |
JDK-8230549 | 11.0.6 | Thomas Stuefe | P3 | Resolved | Fixed | b01 |
Description
bufferedStream, in its dynamic variant (where it is supposed to allocate its own buffer from C-Heap) can dynamically grow. It has a "bufmax" parameter which looks like it is supposed to be a limit to the buffer size (defaults to 10M).
bufferedStream(size_t initial_bufsize = 256, size_t bufmax = 1024*1024*10);
However, when growing the buffer it does not honor the bufmax cap. It just grows forever.
That can lead to large memory usage or runaway memory leaks when printing, especially with faulty printing code.
bufferedStream(size_t initial_bufsize = 256, size_t bufmax = 1024*1024*10);
However, when growing the buffer it does not honor the bufmax cap. It just grows forever.
That can lead to large memory usage or runaway memory leaks when printing, especially with faulty printing code.
Attachments
Issue Links
- backported by
-
JDK-8230549 bufferedStream does not honor size limit
-
- Resolved
-
-
JDK-8232212 bufferedStream does not honor size limit
-
- Resolved
-
- relates to
-
JDK-8224213 various stringStream issues
-
- Resolved
-