<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Modern IDB: Ref-cycles and leaks"
href="https://bugs.webkit.org/show_bug.cgi?id=154015#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Modern IDB: Ref-cycles and leaks"
href="https://bugs.webkit.org/show_bug.cgi?id=154015">bug 154015</a>
from <span class="vcard"><a class="email" href="mailto:beidson@apple.com" title="Brady Eidson <beidson@apple.com>"> <span class="fn">Brady Eidson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=154015#c2">comment #2</a>)
<span class="quote">> 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.</span >
Transactions leak a couple of different ways.
One huge way is that TransactionOperations leak! Yikes. That one is an easy fix.
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Modern IDB: TransactionOperation objects leak"
href="show_bug.cgi?id=154054">https://bugs.webkit.org/show_bug.cgi?id=154054</a> for that</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>