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

Re: [IndexedDB] setVersion blocked on uncollected garbage IDBDatabases

From: Glenn Maynard <glenn@zewt.org>
Date: Wed, 9 Feb 2011 15:56:00 -0500
Message-ID: <AANLkTinaegdRGBXAuBX2GPY513ZA60D2ofTwXQqsTxak@mail.gmail.com>
To: Drew Wilson <atwilson@google.com>
Cc: Jonas Sicking <jonas@sicking.cc>, 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:05 PM, Drew Wilson <atwilson@google.com> wrote:

> This discussion reminds me of a similar issue with MessagePorts. The
> original MessagePort spec exposed GC behavior through the use of onclose
> events/closed attributes on MessagePorts. It turns out that on Chromium,
> there are situations where it's very difficult for us to GC MessagePorts (a
> port's reachability depends on the reachability of the entangled port on an
> entirely separate process), and so we just don't.

Err, so you just leak MessagePorts?  Or just in those situations, whatever
they are?  Does this happen even for the implicit MessagePort associated
with each worker?

Glenn Maynard
Received on Wednesday, 9 February 2011 21:44:40 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:30 UTC