Bug ID: JDK-8161144 Fix for JDK-8147451 failed: Crash in Method::checked_resolve_jmethod_id(

Type: Bug
Component: hotspot
Sub-Component: jvmti
Affected Version: 8u40

Priority: P2
Status: Closed
Resolution: Fixed

Submitted: 2016-07-11
Updated: 2017-11-29
Resolved: 2016-08-15

Versions (Unresolved/Resolved/Fixed)

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 8
8u112 b09Fixed

VisualVM's memory profiling with allocation stacktraces crashes JVM in Method::checked_resolve_jmethod_id() just as described in JDK-8147451. It happens even when using JDK 1.8.0_112b02 with fix for JDK-8147451 integrated.
Tested on Ubuntu 16.04 x64. Log attached.

No issues in recent VM nightly builds. UR SQE OK to take it in PSU16_04.
15-08-2016
Changed the label
12-08-2016
You are requesting this in PSU, but the lable is CPU16_04-critical-request. Should be PSU16_04-critical-request.
11-08-2016
Critical Request Template - Justification : Fix for JDK-8147451 was incomplete, should add this additional fix in order to not have an incomplete fix in - Risk Analysis : Very low. Fix is small and just clears a data structure and changes an assert to a proper null check - Webrev : http://hg.openjdk.java.net/jdk8u/jdk8u-dev/hotspot/rev/1f6b58e0bd06 - Testing (done/to-be-done) : Verify using the steps in JDK-8147451 - Back ports (done/to-be-done) : Done - Fix For Release : JDK 8 PSU
08-08-2016

Duplicate :	JDK-8166448 - Crash in Method::checked_resolve_jmethod_id(_jmethodID*)
Relates :	JDK-8147451 - Crash in Method::checked_resolve_jmethod_id(_jmethodID*)