JDK-8055949 : ByteArrayOutputStream capacity should be maximal array size permitted by VM
- Type: Bug
- Component: core-libs
- Sub-Component: java.io
- Priority: P2
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2014-08-25
- Updated: 2018-07-24
- Resolved: 2014-08-27
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 | JDK 7 | JDK 8 | JDK 9 |
|---|---|---|---|
| 6u95Fixed | 7u76Fixed  |
8u31Fixed |
9 b29Fixed |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
It should be possible to write (almost) Integer.MAX_VALUE bytes to a ByteArrayOutputStream. In fact, because of resizing algorithm, the effective capacity is only half that. ByteArrayOutputStream should use the same resizing computation for huge capacities as is already done in collection classes like ArrayList. Fix is easy. http://cr.openjdk.java.net/~martin/webrevs/openjdk9/ByteArrayOutputStream-MAX_ARRAY_SIZE/
Comments
|