GC log corruption

Kirk Pepperdine kirk at kodewerk.com
Fri Oct 10 19:42:47 UTC 2014


I’ve run into this only once before and only just recently. I didn’t report it the first time because I was unable to get any details and I thought it might be an aberration so…  but this time I’ve got or can get any details needed.

I’ve attached the log produced by a 170_25 JVM running in RHL. The JVM ran out of heap and this is the log that was sent. As you can see it looks as if the middle of the file was over-written by a zero’ed out buffer. Just curious if anyone has reported this or if I need to fill out a bug report.

Kind regards,
Kirk Pepperdine

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 100914-prd-6.1GA2-gc.log
Type: application/octet-stream
Size: 2986263 bytes
Desc: not available
URL: <https://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20141010/521564d2/100914-prd-6.1GA2-gc.log>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20141010/521564d2/signature.asc>

More information about the hotspot-gc-dev mailing list