[Vue warn]: Error in created hook: "QuotaExceededError: The quota has been exceeded."

found in

---> <Sidebar> at src/components/sidebar.vue
       <Root> vue.esm.js:628
DOMException: "The quota has been exceeded." vue.esm.js:1897
    VueJS 23
    createSideMenu adminsidepanelmain.js:68
    createPanelAppliance adminsidepanelmain.js:155
    <anonyme> adminsidepanelmain.js:186
    jQuery 2
[Vue warn]: Error in mounted hook: "QuotaExceededError: The quota has been exceeded."

found in

---> <Submenu> at src/components/subcomponents/_submenu.vue
       <Sidemenu> at src/components/subcomponents/_sidemenu.vue
         <Sidebar> at src/components/sidebar.vue
           <Root> vue.esm.js:628
DOMException: "The quota has been exceeded." vue.esm.js:1897
[Vue warn]: Error in mounted hook: "QuotaExceededError: The quota has been exceeded."

found in

---> <Submenu> at src/components/subcomponents/_submenu.vue
       <Sidemenu> at src/components/subcomponents/_sidemenu.vue
         <Sidebar> at src/components/sidebar.vue
           <Root> vue.esm.js:628
DOMException: "The quota has been exceeded." vue.esm.js:1897
[Vue warn]: Error in mounted hook: "QuotaExceededError: The quota has been exceeded."

found in

---> <Sidemenu> at src/components/subcomponents/_sidemenu.vue
       <Sidebar> at src/components/sidebar.vue
         <Root> vue.esm.js:628
DOMException: "The quota has been exceeded." vue.esm.js:1897
[Vue warn]: Error in mounted hook: "QuotaExceededError: The quota has been exceeded."

found in

---> <Questionexplorer> at src/components/subcomponents/_questionsgroups.vue
       <Sidebar> at src/components/sidebar.vue
         <Root> vue.esm.js:628
DOMException: "The quota has been exceeded." vue.esm.js:1897
[Vue warn]: Error in mounted hook: "QuotaExceededError: The quota has been exceeded."

found in

---> <Sidebar> at src/components/sidebar.vue
       <Root> vue.esm.js:628
DOMException: "The quota has been exceeded." vue.esm.js:1897
[Vue warn]: Error in mounted hook: "QuotaExceededError: The quota has been exceeded."

(found in <Root>) vue.esm.js:628
DOMException: "The quota has been exceeded." vue.esm.js:1897
Unhandled promise rejection DOMException: "The quota has been exceeded." es6.promise.js:110
Unhandled promise rejection DOMException: "The quota has been exceeded." es6.promise.js:110
Erreur dans les liens source : request failed with status 404
URL de la ressource : http://limesurvey.local/develop/assets/packages/bootstrap/bootstrap.css
URL du lien source : bootstrap.css.map
Erreur dans les liens source : request failed with status 404
URL de la ressource : http://limesurvey.local/develop/themes/admin/Sea_Green/css/lime-admin-colors.css
URL du lien source : lime-admin-colors.css.map
Erreur dans les liens source : TypeError: NetworkError when attempting to fetch resource.
URL de la ressource : moz-extension://6887d171-2694-4f4e-a73e-2a09581aa7cd/browser-polyfill.js
URL du lien source : browser-polyfill.js.map
Erreur dans les liens source : request failed with status 404
URL de la ressource : http://limesurvey.local/develop/assets/packages/lstutorial/build/lstutorial.js
URL du lien source : lstutorial.js.map

etc …

Same with debug = 0 after reset assets

Delete whole localStorage fix the issue.

But it must be done transparently for all user/browser

Hmm, do not have this issue (tried it with debug mode 1). COuld you confirm whether you still have it in the latest dev? Or did I test it wrongly... hmm

@cdorin : need localStorage filled by a lot of survey , after a lot of test.
Look at console/localStorage , delete a survey : local storage still there: never deleted.
We must delete local storage : it's caching : we must not take all memory available …

Capture d’écran du 2019-08-21 01-39-51.png (96,353 bytes)   

Capture d’écran du 2019-08-21 01-39-51.png (96,353 bytes)   

thanks @DenisChenu:

"bug" confirmed: got exactly the same error this morning, perhaps because I'm active on many limesurvey instances on the same debian server (all are Version 3.17.16+190906)

using the same method described by Denis (clearing the local storage from ff inspector / storage) worked for me

it was not so obvious to find the fix (tried many things and finally found it by myself... Unfortunately before reaching that post!)

Yep,

We really need to

1. Clean up our localStorage more than currently
2. Maybe find a way to have working LimeSurvey admin without any localStorage …

https://stackoverflow.com/questions/2989284/what-is-the-max-size-of-localstorage-values and https://www.html5rocks.com/en/tutorials/offline/quota-research/
an,d https://demo.agektmr.com/storage/

Maybe move to sessionStorage : https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage

Thanks Denis for the interesting links; I must confess, 'till this morning I didnt knew anything about localStorage... so now I know a bit more - and still haven't understood the utility of this feature, and I particularly don't understand why LS need that stuff.

Wouldn't it be possible to store that in a session table on the server? A table which could be automatically emptied after a couple of days or a given period, defined in some LS config - you know, kind of a "good old time", when sessions where stored on the server, with just a simple cookie linking the client to the datas in the table? Ok, someone may argue that this means a little more usage of bandwidth, but it is really there that we need to try to minimize bandwith usage?

My dinosaur-old-way-of.thinking doesn't really like that new wave of excessive usage of client-side datas - and this is getting harder with working with many different devices on different places, which is (unfortunately or not) a trend that will likely increase in the future

Hi Frederic, it's not for you, more for dev team :)

And about your issue «Maybe find a way to have working LimeSurvey admin without any localStorage …»

I cant reproduce it.

@JHoeck

I cant reproduce it.

You need a lot lot lot of survey testing for this issue … html5rocks show it broke when get to 10MB with firefox and chrome.

A solution to get it quickly

Capture d’écran du 2019-10-04 09-02-49.png (8,061 bytes)   

Capture d’écran du 2019-10-04 09-02-49.png (8,061 bytes)   

And with dom.storage.enabled to false : no alert are shown, something like “Sorry, you need to activate localStorage” ?
(In my opinion : must work without local storage … (and without JS too …))

Capture d’écran du 2019-10-04 09-04-11.png (3,107 bytes)   

Capture d’écran du 2019-10-04 09-04-11.png (3,107 bytes)   

dom.storage.enabled to false : issue in 3.8 too

Again now, just after create a new survey with "sample question"

Console error are more clear :)

We have this in LS3 too. I set to urgent.

My opinion : we must not use localmStorage for such data, we set in local storage something

• update a lot (if we look at question, in general we edit questin)
• not seen a lot (we look at question one or 2 times not 20 times without update)

And more : localstorage stay in browser ... ; not cleaned when not logued in ...

I have the same problem and can't seem to figure out how to use session storage, this has to be in the server side, right.

No : browser side

According to @ollehar comment
https://bugs.limesurvey.org/view.php?id=15063#c55677

This must be set to 3.X too, no ?

This will be hard to explain to potential clients!!!

The code should automatically purge the storage. A previous coder said it was fixed, but maybe it was not.

I'm using the latest Version 4.1.15+200402 and it is not fixed!

@fjusufi If you're a paying customer, please report it in our support channel.

Not a paying customer, but also experiencing this bug (4.2.2+200504, self-hosted).

@jelle_S Did clearing browser local storage fix it?

Maybe we can automatically clear dom.storage just after login ?

Yes, clearing the storage fixed it, but not an easy process to explain to an end-user :)

Maybe we can automatically clear dom.storage just after login ?

We can also configure VueX to not use local storage!

We can also configure VueX to not use local storage!

Yes , sure .

Since it's updated a lot : each time a question was updated : the storage can be outdated …
I don't understand why we use localstorage ?