JDK-8144445 : Maximum size checking in Marlin ArrayCache utility methods is not optimal
- Type: Bug
- Component: client-libs
- Sub-Component: 2d
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-12-01
- Updated: 2021-06-28
- Resolved: 2015-12-10
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 8 | JDK 9 | Other |
|---|---|---|
| 8u311Fixed | 9 b100Fixed  |
openjdk8u252Fixed |
Related Reports
|
Relates :
|
Description
The checking doesn't allow for MAX_INT to be used as a valid return value (MAX_INT-1 is the largest it will return).
Comments
|