[Webkit-unassigned] [Bug 157448] Modern IDB: IDBRequests that are stop()'ed don't notify the IDBServer of that fact

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 6 22:17:49 PDT 2016


--- Comment #1 from Brady Eidson <beidson at apple.com> ---
There's (3) ActiveDOMObjects in play in the IDB family of objects.

1 - IDBDatabases already close() themselves when the ScriptExecutionContext stops.
2 - IDBTransactions already abort() themselves when the context stops.

When transactions abort, that also happens to clean up *most* of the queued up IDBRequests associated with that transaction.

3 - IDBRequests do *not* do any cleanup when they are stop()'ed. As mentioned above in #2, this is usually not an issue for most requests.

But for IDBOpenDBRequests that have not yet resulted in an open IDBDatabase connection or version change IDBTransaction, they leave the IDBServer in a bad state.

To be conservative to start (and not risk flooding the IDBServer with cross thread traffic or IPC traffic just because of a page navigation), I'll just implement the cleanup in IDBOpenDBRequest.

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/20160507/af3f12d9/attachment.html>

More information about the webkit-unassigned mailing list