Description of problem: - Local offline cache gets corrupted in firefox - javascript throws NS_ERROR_FILE_CORRUPTED Version-Release number of selected component (if applicable): - 4.12.14-300.fc26.x86_64 - firefox-55.0.3-1.fc26.x86_64 How reproducible: - intermittent, seems to occur more frequently with sites that heavily utilize javascript and the local offline datastore - https://stackoverflow.com/questions/18877643/error-in-local-storage-ns-error-file-corrupted-firefox Steps to Reproduce: 1. unsure 2. 3. Actual results: - website stops working properly - Offline cache is corrupted Expected results: - websites work properly - no cache corruption Additional info:
Red Hat Internal: This is a widespread problem for us in support. Internal case management system usability is severely impacted by this to widespread effect. This issue does not seem to be prevalent in Chrome.
Red Hat Internal: As an addition: Ascension: - the issue presents itself as an entirely blank screen when accessing pages Salesforce: - the issue presents itself as an inability to add comments to cases Deleting the offline cache fixes both. You can determine the location of your offline cache by going to about:cache, and looking at the path defined in the appcache section. You will want to delete the index.sqllite file in that directory.
Looks like https://bugzilla.mozilla.org/show_bug.cgi?id=1341070
Context: Hi, I work on the Firefox/Gecko storage subsystems! (In reply to Joe Wright from comment #1) > Red Hat Internal: This is a widespread problem for us in support. Internal > case management system usability is severely impacted by this to widespread > effect. This issue does not seem to be prevalent in Chrome. Are you saying that you are experiencing corruption when using your internal tool, or that the problem is being reported a lot? Related-ly, do you know if: - The profiles of affected users are being stored on NFS or similar remote file-system where locking semantics may be different? - If, because of use of NFS or for other reasons, the preference "storage.nfs_filesystem" is present and set to true in those profiles? ("about:config" can be used to check this.) Also good to know: - Is this exactly the localStorage "NS_ERROR_FILE_CORRUPTED" error, or just something similar? I ask because we've been experiencing and are attempting to deal with users jumping between different releases of Firefox with the same profile. You mention Firefox 55, which is notable because we bumped the LocalStorage schema version in Firefox 55, so that if you use a profile in 55, then go back to 54, similar problems will occur. Thanks!
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.