[IndexedDB] Fixed DisjointRangeLockManager usage in IndexedDB
IndexedDBFactoryImpl isn't scoped per origin and so can be used by multiple origins. The original code assumed that it was scoped per origin, so when in actuality it was used by multiple origins, when a single origin requested a lock this could interrupt other origins in certain cases. https://docs.google.com/document/d/1jX6OOQJ0aLrWAeqYLtARXPFawUlJPbHNIKAK-0vmFHU/edit#heading=h.6cqn78xajqmp R=cmp@chromium.org Bug: 934790 Change-Id: I10f3e7c1b43ad7310d8824648575d940568b534d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1487369 Commit-Queue: Daniel Murphy <dmurph@chromium.org> Reviewed-by:Chase Phillips <cmp@chromium.org> Cr-Commit-Position: refs/heads/master@{#638260}
Showing
Please register or sign in to comment