-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 9, 10
-
Component/s: hotspot
-
b166
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8179135 | 10 | Igor Veresov | P2 | Resolved | Fixed | b06 |
| JDK-8178479 | 9 | Igor Veresov | P2 | Resolved | Fixed | team |
A number of jtreg tests ends with SIGSEGV at AOTCodeHeap::next
A specific configuration of various modules aot-compiled was used when problems was introduced(see attached hs_err, which lists loaded libraries).
A specific configuration of various modules aot-compiled was used when problems was introduced(see attached hs_err, which lists loaded libraries).
- backported by
-
JDK-8178479 AOT: SIGSEGV in AOTCodeHeap::next when using specific configuration
-
- Resolved
-
-
JDK-8179135 AOT: SIGSEGV in AOTCodeHeap::next when using specific configuration
-
- Resolved
-
- duplicates
-
JDK-8176888 AOT: SIGSEGV in frame InetAddressHolder.getHostName
-
- Closed
-