-
Enhancement
-
Resolution: Fixed
-
P3
-
None
-
b24
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8348763 | 21.0.8-oracle | Johny Jose | P3 | Resolved | Fixed | b03 |
| JDK-8348764 | 17.0.16-oracle | Johny Jose | P3 | Resolved | Fixed | master |
| JDK-8348765 | 11.0.28-oracle | Johny Jose | P3 | Resolved | Fixed | master |
| JDK-8348766 | 8u461 | Johny Jose | P3 | Resolved | Fixed | master |
For some instances of `BigDecimal`, invoking `toPlainString()` might wrongly result in a `NegativeArraySizeException` when it should, in fact, throw an `OutOfMemoryError` to indicate that the resulting `String` would be too large, that is, consisting of more than `Integer.MAX_VALUE` characters.
- backported by
-
JDK-8348763 Enhance checks in BigDecimal.toPlainString()
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk/a6785e4d
-
Review
openjdk/jdk/16457
-
Review(master)
openjdk/jdk17u-dev/3510
-
Review(master)
openjdk/jdk21u-dev/1676
(3 links to)