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

[IndexedDB] setVersion blocked on uncollected garbage IDBDatabases

From: Jeremy Orlow <jorlow@chromium.org>
Date: Mon, 7 Feb 2011 20:09:26 -0800
Message-ID: <AANLkTimtMj9ZeQAnhVt_dgxQReXNpT=E-2syV_2t_LCL@mail.gmail.com>
To: public-webapps WG <public-webapps@w3.org>
We're currently implementing the onblocked/setVersion semantics and ran into
an interesting problem: if you don't call .close() on a database and simply
expect it to be collected, then you ever being able to run a setVersion
transaction is at the mercy of the garbage collecter doing a collection.
 Otherwise implementations will assume the database is still open...right?

If so, this seems bad.  But I can't think of any way to get around it.
 Thoughts?

J
Received on Tuesday, 8 February 2011 04:10:15 GMT

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