New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 736945 link

Starred by 3 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

chrome.storage.local.remove doesn't work if CrOs device is full

Project Member Reported by drustsm...@google.com, Jun 27 2017

Issue description

Chrome Version: 59.0.3071.93
OS: CrOs  9460.61.0	

What steps will reproduce the problem?
(1) Add storage and unlimitedStorage permissions to a chrome app.
(1) Fill up the device, I used `df -h` to get available space in /var then ran `fallocate -l 50M /var/log/big_file` to fill it up almost all the way.
(2) Use  chrome.storage.local.set(...) to fill it up the rest of the way, until you get an error. IO error: ... FILE_ERROR_NO_SPACE...
(3) Try to use chrome.storage.local.remove(...) to remove data saved in previous step.

What is the expected result?
You should be able to remove the data to help clear space.

What happens instead?
You get an error, there is no space to remove an element:
Unchecked runtime.lastError while running storage.remove: IO error: .../000120.ldb: FILE_ERROR_NO_SPACE (ChromeMethodBFE: 3::WritableFileAppend::8)


This bug makes it possible to fill up a device too far, and then not be able to fix it because you can no longer remove items from storage.

Cannot workaround and stop saving before filling up due to this bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=420633&q=chrome.system.storage&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified

API docs:
https://developer.chrome.com/extensions/storage

 
Project Member

Comment 1 by sheriffbot@chromium.org, Jul 12 2017

Labels: Hotlist-Google

Comment 2 by r...@chromium.org, Oct 4 2017

Owner: agawronska@chromium.org
Status: Assigned (was: Untriaged)
Cc: michae...@chromium.org
Components: -Platform>Apps>API Platform>Extensions>API
Status: Started (was: Assigned)
Cc: weifangsun@chromium.org
Hi, just checking in on this bug - Was this fixed/Is this still being worked on?

Sign in to add a comment