JDK-6968383 : jvmti exception dispatch tracking still forces deopt in some cases
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: hs19
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2010-07-12
  • Updated: 2025-10-03
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
tbdUnresolved
Related Reports
Relates :  
JDK-6902182 - Starting with jdwp agent should not incur performance penalty
Description
The fix for 6902182 removed most of the penalty for running with an agent but it's still the case that the exception paths in the runtime may force a deopt to avoid double notifies.  Some better strategy for avoiding these would remove the last penalty.
Comments
Removed - svc-close label. This is still a valid enhancement.
03-10-2025
Not sure, we have resources to fix this in 10, moving to 11.
14-04-2017