CacheStorageCache::Close should prevent future operations from scheduling |
|||||
Issue descriptionCacheStorageCache::Close schedules a close operation. Between when the Close is scheduled and when it actually runs, more operations might be put on the queue. Those operations won't get a chance to run if Close's callback immediately deletes the cache object. We should alter Close() to set a "closing_" variable which prevents future operations from scheduling, instead they'll immediately run their callbacks with an error state. Then it's safe to delete the CacheStorageCache object once Close() runs its callback.
,
Jul 28 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 11 2017
,
Aug 13
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 18
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jkarlin@chromium.org
, Jul 27 2016Labels: OS-All
Status: Available (was: Untriaged)