Indexed DB: Prevent invalid transaction aborts
During upgrade transactions, a store or index can be created and then immediately used from script in operations (e.g. "count"). On the backend, the creation will not run until the transaction acquires a lock, and pending tasks are queued. A handful of operations (including "count()") were synchronously checking to see if the target store/index had been created before queuing the task, which would fail if the lock had not yet been acquired. The checks must occur when the task is run; remove the bogus early checks, which would abort the transaction. Bug: 1045585 Change-Id: Ibef191e24916333da4e9b2449dda5ff775a35138 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023521Reviewed-by:Daniel Murphy <dmurph@chromium.org> Commit-Queue: Daniel Murphy <dmurph@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#736126}
Showing
Please register or sign in to comment