JDK-8136991 : [REDO] Additional number of processed references printed with -XX:+PrintReferenceGC after JDK-8047125
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-09-23
  • Updated: 2018-06-21
  • Resolved: 2015-09-28
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 9
9 b89Fixed
Related Reports
Cloners :  
JDK-8133818 - Additional number of processed references printed with -XX:+PrintReferenceGC after JDK-8047125
Description
JDK-8047125 separated processing of j.l.ref.PhantomReference and Cleaner into two separate phases during reference processing.

This resulted in -XX:+PrintReferenceGC output to be scrambled slightly, adding a new "refs: <count>" string to the PhantomReference section.

Example:
7.642: [SoftReference, 0 refs, 0.0006965 secs]7.643: [WeakReference, 40 refs, 0.0003039 secs]7.643: [FinalReference, 3477 refs, 0.0036191 secs]7.647: [PhantomReference, 0 refs, 0 refs, 0.0006649 secs]7.647: [JNI Weak Reference, 0.0000119 secs], 0.0173298 secs]

Cleaners should have their own section in the printout.
Comments
ILW - L (output is scrambled which may break some VGC processing tools) L=Low, only with -XX:+PrintReferenceGC M (use less PGC thread count should avoid it, but that is a hassle) -> P5
23-09-2015