GC log file corruption

Kirk Pepperdine kirk at kodewerk.com
Fri May 9 09:07:31 UTC 2014


I found this in 1.7.0_51 (OSX)

12.590: [GC concurrent-root-region-scan-start]
12.590: [Full GC (System.gc())12.591: [GC concurrent-root-region-scan-end, 0.0012580 secs]
12.591: [GC concurrent-mark-start]
 5221K->4963K(16M), 0.0284460 secs]
   [Eden: 1024.0K(5120.0K)->0.0B(6144.0K) Survivors: 1024.0K->0.0B Heap: 5221.0K(16.0M)->4963.9K(16.0M)]
 [Times: user=0.04 sys=0.00, real=0.03 secs] 
12.619: [GC concurrent-mark-abort]

The Full GC has been corrupted by the concurrent-root-region-scan-end.

Is it worthwhile filing a bug on this or is this type of record corruption considered to be acceptable?

Kind regards,

More information about the hotspot-gc-dev mailing list