New issue
Advanced search Search tips

Issue 644750 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Put operations run out-of-order

Project Member Reported by jkarlin@chromium.org, Sep 7 2016

Issue description

CacheStorageCache::BatchOperation will delay scheduling Put operations until after first checking with the quota manager to see how much space is left. Other operations don't have to delay on the quota manager and schedule immediately, meaning an operation that is started after a put might actually get scheduled before the put.

This is a complex problem. The QuotaManager might schedule a size operation on the CacheStorageCache, which must complete for the Put to begin. So we can't make the QuotaManager call a part of a scheduled operation.

 
It looks like there is a second place that put operations are scheduled asynchronously. In Cache::putImpl, Blink will asynchronously create a blob handle if the put operation has a response body before dispatching the put, otherwise it will immediately dispatches.
Status: WontFix (was: Available)
This isn't actually a bug. There is nothing in the spec preventing operations from running in parallel where possible (in fact, the plan is to implement that at some point). Therefore it's reasonable for later operations to start before earlier operations. 

Sign in to add a comment