ParNew promotion failed, no expected OOM.

Dawid Weiss dawid.weiss at gmail.com
Wed Apr 11 11:31:36 PDT 2012


> GC has competed, as a percentage of the old gen capacity. It almost seems as
> though you have a largish object in the young gen which will not fit in the space
> free in the old gen, o it will never be promoted unless sufficient space clears up in the old

Yes, this is exactly the case -- there is a recursive routine that
builds a complex array-based data structure. The routine is recursive
and I'm guessing the old gen is already filled up with other data so
there is no space to fit the new array there.

> I think we need to fix the space criteria for overhead limit to deal
> gracefully with these kinds of situations.

This would make sense even if it's really an outlier observation of
mine (I'm specifically trying to reach heap boundary; not a typical
use case I guess).

> On an unrelated note, for such a small heap, you should probably use
> ParallelOldGC rather than CMS, but I realize that you didn't explicitly ask for CMS, the mac just
> gave it to you because that's the default.

This happened on a mac and on ubuntu linux as well, but it's indeed of
no relevance here because it's the default setting and this is what is
worrying. I also figured that switching the garbage collector will be
a temporary solution (I used the good old serial gc since I don't care
about timings here).

Thanks for confirming my suspicions.

Dawid


More information about the hotspot-gc-use mailing list