Bug 186180 - IDBTransaction randomly hangs for concurrent operations
Summary: IDBTransaction randomly hangs for concurrent operations
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: Safari 11
Hardware: Mac macOS 10.13
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-31 19:38 PDT by Ian Weng
Modified: 2018-05-31 19:38 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Weng 2018-05-31 19:38:27 PDT 
The bug was found while using localForage: https://github.com/localForage/localForage
Initially I thought it was a localForage bug, but after play around, I believe it should belong to WebKit.

Basically none of IDBTransaction onabort/onerror/oncomplete are fired. 

https://github.com/localForage/localForage/issues/824  
My testing code can reproduce the bug (it passes in FF and Chrome)

https://github.com/localForage/localForage/pull/825
Doing this (referencing transaction in a global object) makes my testing code pass but I don't understand and guess the transaction could be garbage collected too early (before oncomplete being dispatched to event loop)

Let me know if you want some code getting rid of localForage (purely indexeddb), I am happy to do that but not sure whether it is needed at current stage.

Environments:
mac OS 10.13.4 (17E202), also tried r232383 High Sierra on it
iOS 11.3.1 (15E302)