JDK-8266453 : Shenandoah: Disable write protections before patching nmethod in nmethod_barrier on MacOSX/AArch64
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: os_x
- CPU: aarch64
- Submitted: 2021-05-03
- Updated: 2021-05-10
- Resolved: 2021-05-05
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 17 |
|---|
17 b21Fixed  |
Related Reports
|
Relates :
|
Description
# # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0x00000001084d95e4, pid=49007, tid=8451 # # JRE version: OpenJDK Runtime Environment (17.0) (fastdebug build 17-internal+0-adhoc.zgu.jdk) # Java VM: OpenJDK 64-Bit Server VM (fastdebug 17-internal+0-adhoc.zgu.jdk, mixed mode, tiered, compressed oops, compressed class ptrs, shenandoah gc, bsd-aarch64) # Problematic frame: # V [libjvm.dylib+0xcd95e4] nmethod::is_unloading()+0xc0 # # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /Users/zgu/Documents/workspace/jdk/build/macosx-aarch64-server-fastdebug/test-support/jtreg_test_jdk_tier1/scratch/2/hs_err_pid49007.log # # If you would like to submit a bug report, please visit: # https://bugreport.java.com/bugreport/crash.jsp #
Comments
|