JDK-8139379 : Tests fail with assert(nm->insts_contains(original_pc)) failed: original PC must be in nmethod
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jfr
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2015-10-12
  • Updated: 2017-08-16
  • Resolved: 2016-06-20
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 9
9 b127Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (C:\jprt\T\P1\192118.iggy\s\hotspot\src\cpu\x86\vm\frame_x86.cpp:406), pid=617204, tid=136056
#  assert(nm->insts_contains(original_pc)) failed: original PC must be in nmethod
#
# JRE version: Java(TM) SE Runtime Environment (9.0) (build 1.9.0-internal-fastdebug-20151009192118.iggy.8136725-b00)
# Java VM: Java HotSpot(TM) Server VM (1.9.0-internal-20151009192118.iggy.8136725-b00, compiled mode, tiered, g1 gc, windows-x86)
Comments
http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=1494298.JAVASE.NIGHTLY.VM.Main_Baseline-RT.2016-06-15-63 Local var @ rbx Type frame* +0x000 _sp : 0x000000b9`8c2bef08 -> 0n798479293331 +0x008 _pc : 0x000000b9`e9131b93 "H???" +0x010 _cb : 0x000000b9`e9131810 CodeBlob +0x018 _deopt_state : 0 ( not_deoptimized ) +0x020 _fp : 0x00000000`00000002 -> ?? +0x028 _unextended_sp : 0x000000b9`8c2bef08 -> 0n798479293331 0:016> u 0x000000b9`e9131b93 000000b9`e9131b93 48832c2405 sub qword ptr [rsp],5 000000b9`e9131b98 e9c38c56f8 jmp 000000b9`e169a860 000000b9`e9131b9d f4 hlt 000000b9`e9131b9e f4 hlt 000000b9`e9131b9f f4 hlt 000000b9`e9131ba0 b0f5 mov al,0F5h 000000b9`e9131ba2 a1f4b90000000086e7 mov eax,dword ptr [E78600000000B9F4h] 000000b9`e9131bab 8bb9000000ff mov edi,dword ptr [rcx-1000000h] 0:016> u 0x000000b9`e9131b93 - 0x5 000000b9`e9131b8e e800000000 call 000000b9`e9131b93 <<-- 000000b9`e9131b93 48832c2405 sub qword ptr [rsp],5 000000b9`e9131b98 e9c38c56f8 jmp 000000b9`e169a860 // nmethod ... _mark_for_deoptimization_status : 1 ( deoptimize ) _deopt_handler_begin : 0x000000b9`e9131b8e "???" 0x000000b9`e9131b8e + 0x5 == 0x000000b9`e9131b93
16-06-2016

Got it.
22-12-2015

[~twisti], see the comments in JDK-8138847.
22-12-2015

Why was this bug filed in hotspot/jfr?
22-12-2015

ILW = M (Crash in debug) M (kitchensink tests) H (no workaround) = P3
12-10-2015