JDK-8223585 : vmTestbase/runtime/pcl/* get SEGV in MetadataOnStackClosure::do_metadata(Metadata*)+0x0
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 13
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-05-08
  • Updated: 2020-02-11
  • Resolved: 2019-05-16
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.
JDK 13
13 b22Fixed
Related Reports
Relates :  
Relates :  
Description
Tests failed with 
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007feb70bb6140, pid=32200, tid=32209
#
# JRE version: Java(TM) SE Runtime Environment (13.0) (build 13-internal+0-2019-05-05-2029021.leonid.mesnik.jdk)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (13-internal+0-2019-05-05-2029021.leonid.mesnik.jdk, compiled mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0xb13140]  MetadataOnStackClosure::do_metadata(Metadata*)+0x0
#
# Core dump will be written. Default location: /scratch/opt/mach5/mesos/work_dir/slaves/df27b84d-b5c1-4760-9e48-df95fd33274c-S106/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/750923e2-4490-4be6-a3d9-6465a4337f6c/runs/297ddcf6-93d0-48a5-8c8a-5a3eaa7ad595/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_vmTestbase_vm_parallel_class_loading/scratch/1/core.32200
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Comments
As I remember the any of test names are not confidential info so we could have them even in open bugs.
09-05-2019

Maybe related to linked bug.
09-05-2019

Seems failure happened with product binaries only.
08-05-2019