-
Bug
-
Resolution: Fixed
-
P2
-
11.0.9, 16, 17
-
b25
-
x86_64
-
linux_ubuntu, windows_10
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8268415 | 16u-cpu | Adam Farley | P2 | Resolved | Fixed | master |
JDK-8268317 | 16.0.2 | Adam Farley | P2 | Closed | Fixed | b07 |
JDK-8269894 | 11.0.13-oracle | Tobias Hartmann | P2 | Closed | Fixed | b02 |
JDK-8268338 | 11.0.13 | Adam Farley | P2 | Resolved | Fixed | b01 |
Correct toString() return value: "java.lang.StringIndexOutOfBoundsException: String index out of range: -2147483648"
Incorrect toString() return value:
"java.lang.StringIndexOutOfBoundsException: String index out of range: -2"
This error does not occur on JDK8, but does occur in 4 out of 5 complete runs on JDK11, and all runs on JDK16.
On JDK11 we see the failure once between 10k and 20k, and on JDK16 and 17 we see the failure once between 10k and 20k, with continuous occurrences starting around the 30k-40k mark.
(A minimal testcase will be attached. I limited the failures to 20 to avoid swamping. Feel free to edit as needed.)
Since this bug doesn't occur when the jit is disabled, and the occurrences only start around the 10k mark, I'm assuming this is a JIT defect. Will ask the community if anyone with JIT skills could take a look.
- backported by
-
JDK-8268338 PhaseStringOpts::int_stringSize doesn't handle min_jint correctly
- Resolved
-
JDK-8268415 PhaseStringOpts::int_stringSize doesn't handle min_jint correctly
- Resolved
-
JDK-8268317 PhaseStringOpts::int_stringSize doesn't handle min_jint correctly
- Closed
-
JDK-8269894 PhaseStringOpts::int_stringSize doesn't handle min_jint correctly
- Closed
- relates to
-
JDK-8141132 Integration
- Resolved
-
JDK-8306007 java/lang/String/concat/IntegerMinValue.java fails on AIX
- Closed
- links to
-
Commit openjdk/jdk11u-dev/d3a5ed2f
-
Commit openjdk/jdk16u/d2d95335
-
Commit openjdk/jdk/d47a77d2
-
Review openjdk/jdk11u-dev/18
-
Review openjdk/jdk16u/127
-
Review openjdk/jdk/4255