RFC 7038914: VM could throw uncaught OOME in ReferenceHandler thread

Thomas Schatzl thomas.schatzl at oracle.com
Tue May 7 15:09:05 UTC 2013


On Tue, 2013-05-07 at 16:10 +0200, Peter Levart wrote:
> On 05/07/2013 03:26 PM, Thomas Schatzl wrote:
> > Hi,
> > There is a message emitted by the VM reading "java.lang.OutOfMemoryError
> > thrown from the UncaughtExceptionHandler in thread "Reference Handler""
> > that is sufficient to detect the problem itself (at least if you enable
> > some flags).
> >
> > I will look at it again and report back if it can be used in some way.
> On my computer the test always produced the same result. So it's pretty 
> reliable. The trick is in fillHeap() method that fills the heap so that 
> even "new Object[1]" throws OOME. Throwable object takes at least the 
> same space as Object[1];

It is fine, thanks. Since you're openjdk author already (plevart?), I
will set you as author for the change - as you both provided the fix as
well as the reproducer.

I merely added boilerplate code.

I will provide a webrev as soon as a jprt run goes through.

Thanks everyone,

More information about the hotspot-gc-dev mailing list