browser.storage.local.set throw "An unexpected error occurred" in linux
Categories
(WebExtensions :: Frontend, defect)
Tracking
(Not tracked)
People
(Reporter: drive4ik, Unassigned)
References
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
try to save data into local storage in linux and then try to save data again
Actual results:
browser.storage.local.set throw "An unexpected error occurred"
Expected results:
Bug in Firefox 71 stable in only in linux.
Tested on Fedora 31 - Always replicated.
Windows - no error
Mac - not tested
Please see attached archive with simple example
Please fix it, this bug broken my addon Simple Tab Groups
Please see latest archive
firefox-bug-save-local-storage-2.zip
(I fix button click, in a hurry, sorry)
Comment 4•6 years ago
|
||
Here are reports of other extensions breaking in Firefox 71 in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1779570
https://bugzilla.redhat.com/show_bug.cgi?id=1779762
I guess the root cause could be the same. One of the affected people says he can only see the problem with Fedora's Firefox, and not official Mozilla's Firefox, so this might be a downstream issue.
Vitaliy, which distribution (and version) have you used?
Hi Kamil!
I downloaded from official site https://getfedora.org/workstation/download/
Fedora-Workstation-Live-x86_64-31-1.9.iso
install it on VirtualBox 6, uninstall Firefox v69 in Fedora update center and then install again Firefox v71 in Fedora update center .
Also, people write to me in the mail that openSUSE Leap 15.1 also does not work
I just downloaded the official release from https://www.mozilla.org/en-US/firefox/new/ and installed it on linux mint with latest updates - there is no error, everything works
Firefox 71 from https://www.mozilla.org/en-US/firefox/new/ also worked in Fedora 31...
but Firefox 71 installed from Fedora apps center - not worked..
I have no idea what it depends on ...
Comment 6•6 years ago
|
||
Another report of this seems to be in bug 1601424
Comment 7•6 years ago
|
||
Please leave the setting of the priority flag to the triage owner. :jimm, you may reset this to P1 anyway, since this affects a lot of extensions, and also web applications like https://riot.im.
Comment 8•6 years ago
|
||
This is caused by Bug 1601707 - gcc miscompilation so it's not a Mozilla bug.
Comment 9•6 years ago
|
||
bug #1601707 talks about a segfault, but I do not experience a browser crash.
Comment 10•6 years ago
|
||
Moreover, Martin Stransky in Red Hat Bugzilla says "it does not look like a gcc regression".
Comment 12•6 years ago
|
||
(In reply to sergio from comment #10)
Moreover, Martin Stransky in Red Hat Bugzilla says "it does not look like a gcc regression".
I was wrong, it's a gcc bug and it's tracked as Bug 1601707.
Updated•6 years ago
|
Description
•