(Preliminary) RFC 7038914: VM could throw uncaught OOME in ReferenceHandler thread

Vitaly Davidovich vitalyd at gmail.com
Sat May 4 17:38:21 UTC 2013

Oops, that was my mistake - I thought the lock here was a j.u.c.Lock which
of course doesn't even make sense given we're talking about ObjectMonitor.
So disregard that bit.

Ignoring OOM and continuing just seems very fragile as it means you somehow
know that all state is still consistent.  Most java code isn't async
exception safe, so it's hard to reason about state after OOM.  Maybe
Reference Handler is OK in that regard though.



Sent from my phone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20130504/b94903aa/attachment.htm>

More information about the hotspot-gc-dev mailing list