JDK-7032407 : Crash in LinkResolver::runtime_resolve_virtual_method()
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: linux_2.6
  • CPU: x86
  • Submitted: 2011-03-30
  • Updated: 2011-07-29
  • Resolved: 2011-04-30
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 7 Other
7Fixed hs21Fixed
Related Reports
Relates :  
Description
There is a JVM crash while doing profiling with VisualVM. See attached hs_err file. Steps to reproduce:
1) Download and install VisualVM 1.3.2 from http://visualvm.java.net
2) start VisualVM
3) start Java2Demo: bin/java -jar demo/jfc/Java2D/Java2Demo.jar
4) in VisualVM open Java2Demo application, go to profier tab and click CPU button.

The crash can be reproduce only if the class data sharing is enabled. This is regression from b129. b128 works fine with class data sharing enabled. Looking at the bugs fixed in b129, CR 6990754 looks like it may cause this regression.

Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/8ce625481709
20-04-2011

EVALUATION Summary: Make CDS reorder vtables so that dump time vtables match run time order, so when redefine classes reinitializes them, they aren't in the wrong order. Reviewed-by: dcubed, acorn
15-04-2011

EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/8ce625481709
15-04-2011

WORK AROUND Running profiled application with disbaled class data sharing (-Xshare:off) will work-around this JVM crash.
30-03-2011