New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Assigned
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Sign in to add a comment

No way to test 'QuotaExceededError'

Reported by, Mar 30 2017 Back to list

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
We recently launched a large PWA at

Some users are reporting it crashes with "QuotaExceededError". Presumably they don't have much disk space or something like that, but obviously this shouldn't crash the app and should be handled elegantly. However it's not clear how to develop this feature.

What is the expected behavior?
Dev tools should have a way to set the available storage quota to something very low like 1kb. Then we can simply try testing our app and see real QuotaExceededError exceptions and make sure they don't bring down the whole app.

What went wrong?
No idea what to do to fix these exceptions.

Did this work before? No 

Chrome version: 57.0.2987.133  Channel: stable
OS Version: 10.0
Flash Version:
Labels: Needs-Triage-M57
Labels: Needs-Feedback
Reporter@ Could you please help us by providing sample crash ID's from chrome://crashes for further investigation.


Comment 3 by, Mar 31 2017

By crash I just mean an unhandled Javascript exception, not a Chrome crash.
Project Member

Comment 4 by, Mar 31 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "" to the cc list and removing "Needs-Feedback" label.

For more details visit - Your friendly Sheriffbot
Labels: TE-NeedsTriageHelp
Status: Assigned (was: Unconfirmed)

Sign in to add a comment