W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: [IndexedDB] setVersion blocked on uncollected garbage IDBDatabases

From: Drew Wilson <atwilson@google.com>
Date: Wed, 9 Feb 2011 14:14:03 -0800
Message-ID: <AANLkTimKPGhB-bU=x-4hb1AT=z=ni02_TCBCukOy1uH8@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Glenn Maynard <glenn@zewt.org>, Jeremy Orlow <jorlow@chromium.org>, ben turner <bent.mozilla@gmail.com>, Joćo Eiras <joao.eiras@gmail.com>, public-webapps <public-webapps@w3.org>
On Wed, Feb 9, 2011 at 2:03 PM, Jonas Sicking <jonas@sicking.cc> wrote:

>
> For what it's worth, shared workers already expose GC behavior. You'll
> get a already-existing shared worker, or a new one will be created,
> depending on if GC has collected the worker or not.
>

Hmmm. That was certainly not the intent when I was discussing the WebKit
implementation with Hixie, but either there was a miscommunication or the
definition of when a document becomes "discarded" has changed since then. In
the WebKit implementation, SharedWorker lifecycle is not tied to GC, but is
instead tied to specific deterministic navigation/close actions on the
parent document.

Dependence of SharedWorkers on GC is bad for all the same reasons I outlined
above - I'll follow up in a separate thread whether that is indeed the
intent of the spec.


> Not saying that this is great, just pointing out that this is the case.
>
> / Jonas
>
Received on Wednesday, 9 February 2011 22:16:04 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT