JDK-6980039 : Refs are not cleared when they should be
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs19
  • Priority: P2
  • Status: Closed
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2010-08-25
  • Updated: 2010-09-09
  • Resolved: 2010-09-09
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
hs20Resolved
Related Reports
Relates :  
JDK-6858496 - Clear all SoftReferences before reaching the GC overhead limit.
Description
The program in the comments section, courtesy of ###@###.###,
throws an OOM when it should not. The bug seems to have first appeared
in 6u18 (hs16), and is present in all subsequent releases. As far as
I can tell the bug is not present in releases prior to and including
6u17 (hs14.3).
I am adding another program, courtesy of ###@###.### / ###@###.###,
where WeakRefs are not cleared when their referents are not reachable. The program is in the
comments section. In this case, reference processing reports that the referents are unreachable
and that it has cleared the referents, yet the subsequent get() returns a non-NULL reference.
Comments
EVALUATION The test programs were modified to work as intended, and showed that references are indeed being cleared as expected. Closing as NAD.
09-09-2010