JDK-6788527 : Server vm intermittently fails with assertion "live value must not be garbage" with fastdebug bits
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs14
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: linux
  • CPU: x86
  • Submitted: 2008-12-23
  • Updated: 2011-03-08
  • Resolved: 2011-03-08
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 JDK 7 Other
6u18Fixed 7Fixed hs16Fixed
Related Reports
Relates :  
JDK-6597109 - "live value must not be garbage" assertion failure
Description
Server vm could fail with following assertion:

#  Internal Error (/BUILD_AREA/jdk7/hotspot/src/share/vm/opto/parse1.cpp:1610), pid=6861, tid=2693622672
#  Error: assert(n != top() || r->in(pnum) == top(),"live value must not be garbage")
Comments
PUBLIC COMMENTS Problem: Jvmti and DTrace threads may change global flags used by Compiler in the middle of compilation. These leads to inconsistent answers from MethodLiveness which leads to the failure during parsing. It also invalidates dependencies constructed during compilation. Solution: Cache Jvmti and DTrace flags used by Compiler at the start in the ciEnv and validate them at the end of the compile.
08-05-2009
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/c96bf21b756f
08-05-2009
EVALUATION The value of JvmtiExport::can_access_local_variables() is changing in the middle of a compile. These leads to inconsistent answers from MethodLiveness which leads to failure in the merge code. If the values of JvmtiExport flags can change during a compile we need to cache them at the start in the ciEnv and validate them at the end of the compile, just like we do for other state.
29-04-2009