[Webkit-unassigned] [Bug 154015] Modern IDB: Ref-cycles and leaks
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Feb 9 16:55:18 PST 2016
https://bugs.webkit.org/show_bug.cgi?id=154015
--- Comment #4 from Brady Eidson <beidson at apple.com> ---
(In reply to comment #3)
> (In reply to comment #2)
> > Next in line is IDBDatabase:
> >
> > It has a couple of refs that come and go during event dispatch, all nicely
> > balanced.
> >
> > It's initial ref is held as the result of the OpenDBRequest. So as long as
> > the open DB request is cleaned up, we're fine.
> >
> > In the case of an upgrade needed, it's next ref is held by the version
> > change IDBTransaction.
> >
> > And, in fact, that ref lasts as long as the transaction object, which is "a
> > very very long time."
> >
> > To see if there's anything circular there, I'll now dig in to the
> > transaction lifetime.
>
> Transactions leak a couple of different ways.
>
> One huge way is that TransactionOperations leak! Yikes. That one is an easy
> fix.
>
> https://bugs.webkit.org/show_bug.cgi?id=154054 for that
So with the fix for 154054, and with the previous fix for IDBOpenDBRequests, the most basic example of IDB usage works without leaks.
Attaching that "basic-test.html" that I've been using so far.
I'll start adding to it now to explore other options in the IDB cloud. (Non OpenDB requests, object stores, indexes, cursors...)
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160210/a64058b0/attachment.html>
More information about the webkit-unassigned
mailing list