JDK-6914436 : 6.0_18-b04 server compiler issue
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 6u18-rev
  • Priority: P2
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows_2003
  • CPU: x86
  • Submitted: 2010-01-06
  • Updated: 2011-02-16
  • Resolved: 2010-04-07
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 6
6-poolResolved
Related Reports
Relates :  
Description
This is a completely different crash. This looks to be a server compiler issue.

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (C:\BUILD_AREA\jdk6_18\hotspot\src\share\vm\code\nmethod.cpp:1836), pid=5588, tid=432
#  Error: guarantee(cont_offset != 0,"unhandled implicit exception in compiled code")
#
# JRE version: 6.0_18-b04
# Java VM: Java HotSpot(TM) Server VM (16.0-b11-fastdebug mixed mode windows-x86 )
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x05d37400):  JavaThread "Thread-3854679" [_thread_in_Java, id=432, stack(0x06d30000
,0x06e30000)]

Stack: [0x06d30000,0x06e30000],  sp=0x06e2f448,  free space=3fd06e2f458k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [jvm.dll+0x5301d2];;  ?report_and_die@VMError@@QAEXXZ+0x4d2
V  [jvm.dll+0x1fc7f1];;  ?report_fatal@@YAXPBDH0@Z+0x41
V  [jvm.dll+0x42a8c1];;  ?continuation_for_implicit_exception@nmethod@@QAEPAEPAE@Z+0x111
V  [jvm.dll+0x49ec04];;  ?continuation_for_implicit_exception@SharedRuntime@@SAPAEPAVJavaThread@@PAE
W4ImplicitExceptionKind@1@@Z+0x1e4
V  [jvm.dll+0x4401c5];;  ?topLevelExceptionFilter@@YGJPAU_EXCEPTION_POINTERS@@@Z+0x325
V  [jvm.dll+0x4416ce];;  ?os_exception_wrapper@os@@SAXP6AXPAVJavaValue@@PAVmethodHandle@@PAVJavaCall
Arguments@@PAVThread@@@Z0123@Z+0x9e
V  [jvm.dll+0x2c5dd9];;  ?call_virtual@JavaCalls@@SAXPAVJavaValue@@VKlassHandle@@VsymbolHandle@@2PAV
JavaCallArguments@@PAVThread@@@Z+0xc9
V  [jvm.dll+0x2c5e57];;  ?call_virtual@JavaCalls@@SAXPAVJavaValue@@VHandle@@VKlassHandle@@VsymbolHan
dle@@3PAVThread@@@Z+0x67
V  [jvm.dll+0x325616];;  ?thread_entry@@YAXPAVJavaThread@@PAVThread@@@Z+0x76
V  [jvm.dll+0x4fe168];;  ?thread_main_inner@JavaThread@@QAEXXZ+0xa8
V  [jvm.dll+0x44128f];;  ?java_start@@YGIPAVThread@@@Z+0xaf
C  [msvcr71.dll+0x9565]
C  [kernel32.dll+0x24829]

Comments
EVALUATION Customer didn't face any crash for one month after disabling the use of native mediaLib library (by using -Dcom.sun.media.jai.disableMediaLib=true). That confirms that native mediaLib library was corrupting the byte-array object headers.
06-04-2010