Bug 158532 - Modern IDB: After a JS breakpoint is hit during an active transaction, the transaction is erroneously flagged as inactive
Summary: Modern IDB: After a JS breakpoint is hit during an active transaction, the tr...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 149117
Blocks: 165889
  Show dependency tree / graph
 
Reported: 2016-06-08 11:40 PDT by Brady Eidson
Modified: 2016-12-14 20:42 PST (History)
1 user (show)

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 Brady Eidson 2016-06-08 11:40:02 PDT 
Modern IDB: After a JS breakpoint is hit during an active transaction, the transaction is erroneously flagged as inactive
Comment 1 Brady Eidson 2016-06-08 11:44:16 PDT 
This is because transactions try to monitor VM scope to deactivate when the VM returns (e.g. event handling, etc etc)

In IDBTransaction::IDBTransaction:
        vm.whenIdle([self, this]() {
            deactivate();
        });

That assumption breaks down during JS debugging.
Comment 2 Brady Eidson 2016-06-08 11:45:29 PDT 
whenIdle() may not do what we want, but we'll need to find a different way.