Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage Exceeds Quota #1586

Closed
jetwes opened this issue Sep 14, 2020 · 7 comments
Closed

Storage Exceeds Quota #1586

jetwes opened this issue Sep 14, 2020 · 7 comments

Comments

@jetwes
Copy link

jetwes commented Sep 14, 2020

Description

In the last couple of days i had several error of this type: "Uncaught DOMException: Failed to execute 'setItem' on 'Storage': Setting the value of 'nnz7zumaz2r' exceeded the quota."

This happens in my testing development after a couple of reloads of my app (always reloading the page with the same livewire component".
After manually deleting the local session storage the error is gone and the component works as expected.

Steps to reproduce

Create a new livewire component and reload your page a couple of times (eg. 20x for example)

Context

  • Livewire version: 2.2.2
  • Laravel version: 7.28.1
  • Browser: Chrome
@elsuterino
Copy link

Have same issue with chrome and firefox. It saves full responses in session and doesn't clean up, after 50-100 it just reaches limits and breaks.

@masterix21
Copy link

I have the same error:

SyncBrowserHistory.js:66 Uncaught DOMException: Failed to execute 'setItem' on 'Storage': Setting the value of '9krvubvjzsa' exceeded the quota.
    at generateNewState (http://myproject.test/vendor/livewire/livewire.js?id=591698dbd067627ac4cf:13:125214)
    at http://myproject.test/vendor/livewire/livewire.js?id=591698dbd067627ac4cf:13:125465
    at http://myproject.test/vendor/livewire/livewire.js?id=591698dbd067627ac4cf:13:2029
    at Array.forEach (<anonymous>)
    at MessageBus.value (http://myproject.test/vendor/livewire/livewire.js?id=591698dbd067627ac4cf:13:1992)
    at Object.call (http://myproject.test/vendor/livewire/livewire.js?id=591698dbd067627ac4cf:13:2822)
    at Object.callHook (http://myproject.test/vendor/livewire/livewire.js?id=591698dbd067627ac4cf:13:6294)
    at new Component (http://myproject.test/vendor/livewire/livewire.js?id=591698dbd067627ac4cf:13:104800)
    at http://myproject.test/vendor/livewire/livewire.js?id=591698dbd067627ac4cf:13:128539
    at Array.forEach (<anonymous>)
generateNewState @ SyncBrowserHistory.js:66
(anonymous) @ SyncBrowserHistory.js:14
(anonymous) @ MessageBus.js:17
value @ MessageBus.js:16
call @ HookManager.js:38
callHook @ Store.js:120
Component @ index.js:46
(anonymous) @ index.js:77
value @ index.js:76
(anonymous) @ setup:1178

@calebporzio
Copy link
Collaborator

Ok, thanks I will look into this today

@nuernbergerA
Copy link
Contributor

Related #1587

@masterix21
Copy link

The problem goes away if you clear the session storage

@calebporzio
Copy link
Collaborator

Ok v2.2.3 only uses sessionStorage if it HAS to, and even then there is a system to clean up old entries if the storage has exceeded the maximum

Closing this. Re-open if persists. Thanks!

@KenKodz
Copy link

KenKodz commented Sep 15, 2020

Thank you Caleb! You rock! I'm going to test the hell out of it tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants