<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 05/04/2013 07:38 PM, Vitaly
Davidovich wrote:<br>
</div>
<blockquote
cite="mid:CAHjP37G2LbwPQAgOo6OcqvBsLPj-T1AdgxC=5GgMWS3Af+4HRg@mail.gmail.com"
type="cite"><!--[if !IE]><DIV style="border-left: 2px solid #009900; border-right: 2px solid #009900; padding: 0px 15px; margin: 2px 0px;"><![endif]-->
<p dir="ltr">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.</p>
<p dir="ltr">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.</p>
<!--[if !IE]></DIV><![endif]--></blockquote>
<br>
I think it is safe to ignore OOME here, since this is the only place
where heap allocation happens and it is known what provokes it.
Otherwise ReferenceHandler just shuffles existing pointers in
existing objects...<br>
<br>
Regards, Peter<br>
<br>
<blockquote
cite="mid:CAHjP37G2LbwPQAgOo6OcqvBsLPj-T1AdgxC=5GgMWS3Af+4HRg@mail.gmail.com"
type="cite"><!--[if !IE]><DIV style="border-left: 2px solid #009900; border-right: 2px solid #009900; padding: 0px 15px; margin: 2px 0px;"><![endif]-->
<p dir="ltr">Cheers</p>
<p dir="ltr">Thanks</p>
<p dir="ltr">Sent from my phone</p>
<!--[if !IE]></DIV><![endif]--></blockquote>
<br>
</body>
</html>