[Webkit-unassigned] [Bug 202705] IndexedDB: on-going IDBTransaction is not active any more after process is suspended

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Oct 9 10:32:41 PDT 2019


--- Comment #5 from Sihui Liu <sihui_liu at apple.com> ---
(In reply to Mauricio W from comment #4)
> I have two related questions:
> 1) Would it be possible to pause an in-progress transaction instead of
> aborting?
No if the process is put suspended.

> 2) In the tests for the patch for 196372
> (https://bugs.webkit.org/show_bug.cgi?id=197050), it is implied that the
> transaction is resumed after being terminated. Is this actually the expected
> functionality, or am I reading this wrong?
> See:
> https://trac.webkit.org/browser/trunk/Tools/TestWebKitAPI/Tests/WebKitCocoa/
> IndexedDBSuspendImminently.html#L27
> https://trac.webkit.org/browser/trunk/Tools/TestWebKitAPI/Tests/WebKitCocoa/
> IndexedDBSuspendImminently.mm#L94)

The test starts 10 transactions, and currently transactions are executed serially on the same database. When process is suspended, we only abort the transaction in progress, and stop starting new transaction. When process is resumed, we start processing new transactions.

That also implies if you have multiple transactions, and if you have never received from callback from requests in some transaction, you don't need to worry about that transaction being aborted because of process suspension.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20191009/8d274c9f/attachment-0001.html>

More information about the webkit-unassigned mailing list