Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8348763 | 21.0.8-oracle | Johny Jose | P3 | Open | Unresolved | |
JDK-8348764 | 17.0.16-oracle | Johny Jose | P3 | Open | Unresolved | |
JDK-8348765 | 11.0.28-oracle | Johny Jose | P3 | Open | Unresolved | |
JDK-8348766 | 8u461 | Johny Jose | P3 | Open | Unresolved |
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()
-
- Open
-
-
JDK-8348764 Enhance checks in BigDecimal.toPlainString()
-
- Open
-
-
JDK-8348765 Enhance checks in BigDecimal.toPlainString()
-
- Open
-
-
JDK-8348766 Enhance checks in BigDecimal.toPlainString()
-
- Open
-
(1 links to)