JDK-8181859 : Monitor deflation is not checked in cleanup path
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-06-09
  • Updated: 2020-11-12
  • Resolved: 2017-06-15
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 10
10 b21Fixed
Related Reports
Relates :  
JDK-8226416 - MonitorUsedDeflationThreshold can cause repeated async deflation requests
Relates :  
JDK-8256304 - should MonitorUsedDeflationThreshold be experimental or diagnostic
Relates :  
JDK-8230938 - Deprecate MonitorBound
Description
Today cleanup is only triggered by IC buffers that needs to be finiliazed.
This cleanup check is done in every GuaranteedSafepointInterval (default 1s).
If the cleanup check return false there will be no safepoint, so the option name, GuaranteedSafepointInterval, is misleading.
This makes the time between safepoint potentials much longer after the compiler stabilize and can have a big negative affect on the numbers of monitor, thus also latency.