cynicaloptimist
Lots of things break when localStorage quota is exceeded
Account Sync is intended to be a workaround for this, but the app does not gracefully handle having too much local content.
Account Sync wouldn't help because it all has to be loaded into local storage, right? If there's too much data to load into local storage, what would the expected behavior be? Is there even a way to recover?
You're exactly right. I have no good answer for the expected behavior here right now. As you've probably noticed with some other bugs regarding duplicate data and entries, a small mitigation would probably be to implement some storage cleanup code. I've historically been very cautious about adding any code that automatically removes stored data.
Hi, Evan: This has caused me to be unable to use Firefox some time ago, but I was able to operate in Chrome. Last night Chrome stopped working for me as well. I have now changed the localStorage default_quota in FF, and that seems to be working. Two questions:
- I have loaded all monster data up to the Tome of Foes, plus the Tome of Beasts. Am I correct that this issue is directly proportional to the size of my 'Creatures' data?
- Do you know how much I can safely increase my default_quota? I am fine with continuing to do so, if it's not going to cause problems elsewhere.
Hi snaggle2th, sorry I overlooked this comment when it was first posted. 'Creatures' takes up a lot of space, but it's worth mentioning that Saved Encounters also save copies of each statblock with the creature that it's attached to, so those can take up a lot of space if you have a lot of them. Not sure about question 2. though.