[whatwg] Workers and queue of events
dimich at chromium.org
Tue Nov 18 22:09:33 PST 2008
Ok, it makes sense for OOM to treat it as other OOM cases.
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?
On Tue, Nov 18, 2008 at 8:15 PM, Robert O'Callahan <robert at ocallahan.org>wrote:
> On Wed, Nov 19, 2008 at 4:44 PM, Dmitry Titov <dimich at chromium.org> wrote:
>> 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.
> 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.
> "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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg