Ok, it makes sense for OOM to treat it as other OOM cases. <div><br></div><div>If I may ask your opinion about related thing: SharedWorkers potentially would run cross-process. IPC can stop/stuck for many reasons, taret process can die in the midflight (killed by the user from TaskManager for example). I guess in this case Worker.postMessage() could still just return as if everything is ok, but nothing would happen. Is it the right behavior?</div>
<div><div><br><br><div class="gmail_quote">On Tue, Nov 18, 2008 at 8:15 PM, Robert O'Callahan <span dir="ltr"><<a href="mailto:robert@ocallahan.org">robert@ocallahan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">On Wed, Nov 19, 2008 at 4:44 PM, Dmitry Titov <span dir="ltr"><<a href="mailto:dimich@chromium.org" target="_blank">dimich@chromium.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
It does seem like OOM indeed but it may be different because with multiple threads it's much easier to get into effects like this, you don't need to allocate a lot of objects.</blockquote><div> </div></div></div>
You're not allocating JS objects but you are allocating event objects internally, and everything's going to work fine until you actually do hit OOM. So I think you should treat it like any other OOM and it should not be exposed to the Web author in any special way.<div>
<div></div><div class="Wj3C7c"><br clear="all">
<br>Rob<br>-- <br>"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]<br>
</div></div></blockquote></div><br></div></div>