Hung JVM consuming 100% CPU

Y. Srinivas Ramakrishna y.s.ramakrishna at
Thu Mar 3 03:01:21 PST 2011

Hi Bogdan --

I agree with Jon that this is not 6692906.
Rather it's a case of a bug in object size computation
causing the GC to go awry. There _were_ a few related
bugs fixed in this area not long ago (in 6u23 i believe),
so I believe you'll find that the upgrade to 6u23
or higher would fix this problem.
If you find that the latest 6uXX update (6u24?) still
exhibits this problem, please file a new bug via your
Java support channel and let us know.

-- ramki

On 3/1/2011 1:38 AM, Bogdan Dimitriu wrote:
> Hi guys,
> We're having a problem with garbage collection as described here:
> (I
> apologise if posting links is not the right policy, but I prefer not to
> duplicate data).
> We are going to try an upgrade to JRE 6u24 soon, but reading the release
> notes for each of the versions since 6u20, I don't have much hope of
> this upgrade fixing the problem.
> I have searched a bit on the Java bugs database and I've come across
> something that looks similar to the problem I am experiencing:
>, but I'm not
> convinced this is exactly the same issue. This bug it seems will be
> fixed in 6u25 (which I've read will be released late March or early April).
> The reason I'm leaning towards thinking this is a JVM bug is the fact
> that the JVM can stay in the hung state (as described on the forum) for
> 2+ hours until we kill the process.
> I was hoping to get an idea about this from the source :), so any hints
> will be greatly appreciated.
> Thanks,
> Bogdan
> _______________________________________________
> hotspot-gc-use mailing list
> hotspot-gc-use at

hotspot-gc-use mailing list
hotspot-gc-use at

More information about the hotspot-gc-dev mailing list