JDK-6964164 : +MonitorInUseLists can cause leakage of contended objects
  • Type: Bug
  • Status: Closed
  • Resolution: Fixed
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P2
  • Affected Version: 6u19-rev
  • OS: generic,solaris_10
  • CPU: generic,sparc
  • Submit Date: 2010-06-25
  • Updated Date: 2011-03-08
  • Resolved Date: 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 Availabitlity Release.

To download the current JDK release, click here.
JDK 7
7Fixed
Related Reports
Duplicate :  
Relates :  
Description
See comments section for emails describing the issue.

Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/bfc89697cccb
2010-07-21

EVALUATION http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/bfc89697cccb
2010-07-15

EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/bfc89697cccb
2010-07-07

EVALUATION Proven cause of memory leak in attached test.
2010-07-01

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?)
2010-06-25