Drop process assertion logic for holding locked files as it is causing issues and should no longer be needed.
Created attachment 389068 [details] Patch
Created attachment 389071 [details] Patch
Created attachment 389074 [details] Patch
Comment on attachment 389074 [details] Patch Will investigate iOS api test failures.
Comment on attachment 389074 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=389074&action=review > Source/WebKit/ChangeLog:22 > + those processes will make sure to suspend their database threads to prevent any I remember further database work would be stopped only when the suspension is imminent or there is no ongoing transaction. If the concept of imminent suspension is still there, we need to also set IsSuspensionImminent::Yes, or set ShouldForceStop::No in WebIDBServer::suspend. A nice thing about having the logic is we don't force aborting ongoing transaction if we know a message of holding file lock has been sent.
Created attachment 397845 [details] Patch
Created attachment 397846 [details] Patch
Committed r260856: <https://trac.webkit.org/changeset/260856> All reviewed patches have been landed. Closing bug and clearing flags on attachment 397846 [details].
<rdar://problem/62558526>
Looks like this got reverted, but the bug is still RESOLVED/FIXED.