JDK-6964164 : +MonitorInUseLists can cause leakage of contended objects
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6u19-rev
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,solaris_10
  • CPU: generic,sparc
  • Submitted: 2010-06-25
  • 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
6u19-crevFixed 7Fixed hs19Fixed
Related Reports
Duplicate :  
JDK-6959550 - Possible memory leak in RMI-IIOP EJB clients in JRE 6u19
Relates :  
JDK-6852873 - Increase in delta between application stopped time and ParNew GC time over application lifetime
Description
See comments section for emails describing the issue.
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/bfc89697cccb
21-07-2010
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/bfc89697cccb
15-07-2010
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/bfc89697cccb
07-07-2010
EVALUATION Proven cause of memory leak in attached test.
01-07-2010
SUGGESTED FIX Upon thread death, the in-use list should be transferred to a global in-use list which will be subject to deflation and eventual flushing to the global free list. (The global free list should be harvested and freed if it grows too large?)
25-06-2010