JDK-5030853 : Lazy deopt and async exceptions cause deopt failures.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-04-13
  • Updated: 2006-01-09
  • Resolved: 2004-04-28
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.
Other
5.0 beta2Fixed
Related Reports
Relates :  
JDK-4991286 - thread misses ThreadDeath of StopThread on Server VM
Relates :  
JDK-5024600 - nsk/jvmti/StopThread/stopthrd007 asserts on solx86
Description
This is a new bug to cover both 4991286 and 5024600 which were incorrectly
closed as duplicates of 5023643. There was no evidence to suggest that
5023643 had async exceptions and the only other thing is common was the
same assert firing as in 5024600. However the assert in 5024600 will fire
for lots a different reasons (much like the reporting of os_solaris.cpp
for all solaris segv's).
This bug affects the following NSK test:

    nsk/jvmti/StopThread/stopthrd007
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta2 FIXED IN: tiger-beta2 INTEGRATED IN: tiger-beta2
14-06-2004
EVALUATION This is a clash between the register contents live at a compiled safepoint and the exception path and deoptimization. Fix is to defer async exceptions so that they registers contents are not destroyed before deopt has a chance to extract them from the deoptee.. ###@###.### 2004-04-13
13-04-2004