According to our Sun contacts, a characteristic of the JVM bug's heap corruption is that the hs err files showed for the heap a high use of eden space,

Below is from hs_err_pid****.log (**** is just a placeholder for the pid number that crashed): Heap PSYoungGen total 1526976K, used 1505255K [0xfffffffef0000000, 0xffffffff50000000, 0xffffffff70000000) eden space 1481024K, 100% used [0xfffffffef0000000,0xffffffff4a650000,0xffffffff4a650000) from space 45952K, 52% used [0xffffffff4d320000,0xffffffff4eac9e00,0xffffffff50000000) to space 45888K, 97% used [0xffffffff4a650000,0xffffffff4d1d59f0,0xffffffff4d320000)

Changes

This is triggered by a bug in Sun JVM garbage collector code in JRE 1.6.0, fixed in 1.6u18-rev(b09) or later.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a Million Knowledge Articles and hundreds of Community platforms