-
Bug
-
Resolution: Fixed
-
P4
-
11, 15
-
b26
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8263675 | 11.0.12-oracle | Dukebot | P4 | Resolved | Fixed | b01 |
JDK-8253515 | 11.0.10 | Stefan Karlsson | P4 | Resolved | Fixed | b01 |
Threads::print_on_error calls Universe::heap()->gc_threads_do(...) without checking the return value of Universe::heap(). Since this function can be called before the heap has been set up, I think we need to NULL check here.
hs_err output from early failure without the fix:
Other Threads:
[error occurred during error reporting (printing all threads), id 0xb, SIGSEGV (0xb) at pc=0x0000000104cbb609]
and with a null check:
Other Threads:
=>0x00007ff10980e220 (exited) JavaThread "Unknown thread" [_thread_in_vm, id=7171, stack(0x00007000083dc000,0x00007000084dc000)]
hs_err output from early failure without the fix:
Other Threads:
[error occurred during error reporting (printing all threads), id 0xb, SIGSEGV (0xb) at pc=0x0000000104cbb609]
and with a null check:
Other Threads:
=>0x00007ff10980e220 (exited) JavaThread "Unknown thread" [_thread_in_vm, id=7171, stack(0x00007000083dc000,0x00007000084dc000)]
- backported by
-
JDK-8253515 Threads::print_on_error assumes that the heap has been set up
-
- Resolved
-
-
JDK-8263675 Threads::print_on_error assumes that the heap has been set up
-
- Resolved
-