[jdk11u-dev] RFR: 8313816: Accessing jmethodID might lead to spurious crashes [v2]
Amos Shi
ashi at openjdk.org
Fri Dec 22 23:01:55 UTC 2023
On Wed, 6 Dec 2023 10:38:56 GMT, Jaroslav Bachorik <jbachorik at openjdk.org> wrote:
>> Looks like a clean backport from the 17u PR, except for replacing nullptr with NULL as you note, and the unused declaration of metaspaceSharedRegionAlignment in WhiteBox.java. The latter doesn't seem have a definition in 11u: if so, please remove it.
>
> @phohensee There are the additional changes in the testing that were necessary. Although they are not affecting any existing code/tests.
Hi @jbachorik,
In today's test result, the test case `test/hotspot/jtreg/serviceability/jvmti/thread/GetStackTrace/GetStackTraceAndRetransformTest/GetStackTraceAndRetransformTest.java` is failing with the following info:
- _Unsupported internal testing APIs have been used._
----------System.out:(20/1185)----------
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc: SuppressErrorAt=/metadataOnStackMark.cpp:50
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (/priv/jenkins/client-home/workspace/openjdk-11u-dev-linux_x86_64-dbg/jdk/src/hotspot/share/classfile/metadataOnStackMark.cpp:50), pid=65261, tid=65413
# assert(SafepointSynchronize::is_at_safepoint()) failed: sanity check
#
# JRE version: OpenJDK Runtime Environment (11.0.23) (fastdebug build 11.0.23-internal+0-adhoc..jdk)
# Java VM: OpenJDK 64-Bit Server VM (fastdebug 11.0.23-internal+0-adhoc..jdk, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Core dump will be written. Default location: /priv/jvmtests/output_openjdk11_dev_dbgU_linuxx86_64/jtreg_hotspot_tier2_work/JTwork/scratch/8/core.65261
#
Unsupported internal testing APIs have been used.
# An error report file with more information is saved as:
# /priv/jvmtests/output_openjdk11_dev_dbgU_linuxx86_64/jtreg_hotspot_tier2_work/JTwork/scratch/8/hs_err_pid65261.log
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
Need your help to identify if this failure is caused by current PR or not.
Thanks
Amos
A Happy Developer
-------------
PR Comment: https://git.openjdk.org/jdk11u-dev/pull/2321#issuecomment-1868118735
More information about the jdk-updates-dev
mailing list