콘텐츠로 건너뛰기
메뉴
커뮤니티에 참여하려면 회원 가입을 하시기 바랍니다.
신고된 질문입니다
1 회신
7373 화면

Hi everyone,

From time to time we get this error - cannot figure out when and how, but it keeps popping up even after we clear all browser cache, cookies and local storage.


Traceback:
Error: The quota has been exceeded.
setItem@https://.../web/content/62624-5a6c6c6/\web\.assets_common\.js\:3821\:385\\
_call_service\@https\:\/\/\.\.\.\/web\/content\/62624\-5a6c6c6\/\web\.assets_common\.js\:3993\:85\\
trigger\@https\:\/\/\.\.\.\/web\/content\/62624\-5a6c6c6\/\
web\.assets_common\.js\:3945\:180\\
_trigger_up\@https\:\/\/\.\.\.\/web\/content\/62624\-5a6c6c6\/\
web\.assets_common\.js\:3951\:378\\
_trigger_up\@https\:\/\/\.\.\.\/web\/content\/62624\-5a6c6c6\/\
web\.assets_common\.js\:3951\:462\\
trigger_up\@https\:\/\/\.\.\.\/web\/content\/62624\-5a6c6c6\/\
web\.assets_common\.js\:3951\:280\\
call\@https\:\/\/\.\.\.\/web\/content\/62624\-5a6c6c6\/\
web\.assets_common\.js\:3993\:372\\
_callLocalStorage\@https\:\/\/\.\.\.\/web\/content\/98914\-0c08dfe\/\
web\.assets_backend\.js\:2700\:235\\
_onPoll\@https\:\/\/\.\.\.\/web\/content\/98914\-0c08dfe\/\
web\.assets_backend\.js\:2707\:676\\
OdooClass\.extend\/\web.assets_common.js:3861:488

_poll/


아바타
취소

Hi Volodymyr,
I am facing the same problem.
Have you found any fix to this issue?
Thanks!

작성자

Yes, still getting it. However it appears not to all users... cannot figure out and reproduce it on other users or test env...

I think it might have something to do with some js modules being added both in common_assets as well as in frontend_assets/backend_assets therefore causing the local storage to fill fast. I am still working on a solution...

베스트 답변

Try this and see if it helps:

on firefox:

  • open tab and navigate to about:config
  • accept warning
  • search for dom.storage.default_quota
  • increase its value (by default its 5120, check for example with 51200)
It seems to work for now however I am not sure that this issue should be fixed from the browser. It is definitely caused by some bad code and should be investigated further.
아바타
취소
작성자

I've changed it in Firefox, however users still get that error... the strange thing is that only few users get it and it doesn't depend on which laptop/computer they login...

What is different to those users? Any security groups or maybe they are portal users? Is there any custom js extension that might store a lot of data locally?

관련 게시물 답글 화면 활동
1
7월 25
2821
0
5월 23
2440
3
3월 25
24419
1
11월 22
2389
1
5월 22
5870