-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 26
-
Component/s: hotspot
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8373665 | 25.0.3-oracle | Jayashree Kumar | P4 | Resolved | Fixed | master |
| JDK-8374156 | 25.0.3 | Paul Hohensee | P4 | Resolved | Fixed | master |
| JDK-8373664 | 21.0.11-oracle | Jayashree Kumar | P4 | Resolved | Fixed | master |
| JDK-8373663 | 17.0.19-oracle | Jayashree Kumar | P4 | Resolved | Fixed | master |
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (c:\sb\prod\1757334802\workspace\open\src\hotspot\share\runtime\safepoint.cpp:663), pid=8596, tid=12032
# fatal error: Safepoint sync time longer than 300.000000 ms detected when executing SafepointALot.
The probolem is that the test internally sets its delays using:
"-XX:SafepointTimeoutDelay=" + Utils.adjustTimeout(300),
"-XX:GuaranteedSafepointInterval=" + Utils.adjustTimeout(300),
which since
- backported by
-
JDK-8373663 Test compiler/loopstripmining/CheckLoopStripMining.java needs internal timeouts adjusted
-
- Resolved
-
-
JDK-8373664 Test compiler/loopstripmining/CheckLoopStripMining.java needs internal timeouts adjusted
-
- Resolved
-
-
JDK-8373665 Test compiler/loopstripmining/CheckLoopStripMining.java needs internal timeouts adjusted
-
- Resolved
-
-
JDK-8374156 Test compiler/loopstripmining/CheckLoopStripMining.java needs internal timeouts adjusted
-
- Resolved
-
- caused by
-
JDK-8260555 Change the default TIMEOUT_FACTOR from 4 to 1
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk25u-dev/77a5421a
-
Commit(master)
openjdk/jdk/06326176
-
Review(master)
openjdk/jdk25u-dev/107
-
Review(master)
openjdk/jdk/27167