QuotaExceededError: Failed to execute 'setItem' on 'Storage'

[VictorienTardif]

I'm getting an error QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value of '@@History/...' exceeded the quota. after having loaded many pages.

Am I doing something wrong or is it a bug?

[mjackson]

I think it's clear from this issue and from #42 that we need a higher level API that helps us manage interfacing with sessionStorage more gracefully than what we have now. Maybe we could keep track of old location keys and expel them if we see this error...

[VictorienTardif]

Is there something I can do in the meantime? Or not at all?
Thank you!

[taion]

I think the right thing to do is to update the check to the one recommended by MDN: https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API/Using_the_Web_Storage_API#Testing_for_support_vs_availability

I'm not aware of any packages that encapsulate this for sessionStorage the way store does for localStorage.

[mjackson]

This issue isn't a question of availability, @taion. We discussed that in #42. This is an actual question of exceeding the available quota in sessionStorage. Sorry if I misunderstood you.

[taion]

Oh, I see - never mind, my bad.

[colindresj]

Running into this quite a bit, so wanted to add a note here to see if there's been more discussion on the right implementation for this

[ryanflorence]

I built a thing a long time ago in coffeescript (heh) that, when the limit was reached, it started pulling out the oldest stuff in there until there was enough room:

https://github.com/ryanflorence/fifo/blob/master/fifo.coffee

Could do something like that.

Also, what are people putting on state? Seems crazy they've got 5 megs! Seems like it's being abused a bit?

[taion]

@ryanflorence We took a stab at this on #104, but it wasn't quite enough. We need to persist in session storage the list of keys to fix both this and #157.

[rpedela]

I am having the same problem. What happens if the oldest entries are removed, and the user clicks the back button enough times? Will the state just be null or will it skip that history entry and go to the next one?

[colindresj]

Agree with @ryanflorence — we've abused the quota, so the exception is legitimate. The way we're fixing this, is by updating our code to be more sensible with what gets persisted throughout the browser session.

With that said, however, the react-router API makes it quite easy to run into that abuse. Having a safety net in place seems important in order to ensure confidence in that ease. Us, as developers, have to be careful about how and what we do, but if history can help out when we're too inattentive to notice, then that's fantastic.