Request for review (and comments) 6302804: Hotspot VM dies ungraceful death when C heap is exhausted in various places.

Joel Borggrén-Franck joel.franck at oracle.com
Tue Dec 21 08:39:50 PST 2010


On 12/20/2010 11:11 PM, coleen phillimore wrote:
> Summary: enhance the error reporting mechanism to direct user to fix the
> problem rather than making it look like a VM error.
>
> I changed the error reporting so that out of swap and out of native (C
> heap) memory doesn't look like a VM assert or look like a
> java.lang.OutOfMemoryError exception that someone could catch. The
> suggested new wording is in the bug link Evaluation section. I'm open to
> rewording if people have strong preferences.

Coleen,

I think the proposed wording is good. The message is comprehensible and 
the proposed solutions are sane.

It would be good however if the 4g process hint was included when 
running on 32 bit VMs.

cheers
Joel Borggrén-Franck
JVM Sustaining Engineering


More information about the hotspot-runtime-dev mailing list