Ns_error_file_corrupted



Ns_error_file_corrupted firefox

Please enable JavaScript in your browser to use all the features on this site.

ClosedBug 583810Opened 11 years agoClosed 11 years ago

Categories

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression. The benefits of membership: Gain access to your control panel and to the box personal messenger Extended profiles with fully editable profile fields The ability to modify their account and notification settings directly from within their profiles Available search The ability to add posts to the blog and write comments.

(Firefox :: General, defect)

For bugs in Firefox Desktop, the Mozilla Foundation's web browser. For Firefox user interface issues in menus, bookmarks, location bar, and preferences. Many Firefox bugs will either be filed here or in the Core product. Bugs for developer tools (F12) should be filed in the DevTools product. (more info)
major

Tracking

()

RESOLVED DUPLICATE of bug 572223

References

()

Summary: Error 400: Bad Request when loading GMail → Error 400: Bad Request when loading GMail -- (NS_ERROR_FILE_CORRUPTED) [nsIBrowserHistory.registerOpenPage]
Closed: 11 years ago
You need to log in before you can comment on or make changes to this bug.

I use Mozilla Firefox as my browser and occasionally I’ve found that certainresources (typically JavaScript or CSS files) may fail to load because of anerror NS_ERROR_FILE_CORRUPTED, which is displayed in the console. For me,this is rarely seen, though I’ve experienced the issue a few times onTrello.com and another on our corporate website CMS. This has the effect ofpreventing whatever that resource was from loading, so in the case of CSS itwon’t display and in the case of JS it won’t run. On Trello, this resulted ina fully broken page — nothing displayed except the header because the wholething is a JS app, and on our CMS, the left-hand navigation was broken becausethat depends on JS too.

To solve this issue, at least for these sites, I opened my console and did the following:

and reloaded the page. Clearing my cache, my browser’s local storage orrestarting the browser was not enough — I expect because the localstorage for these specific sites had become corrupted at some point.Occasionally, running the two commands above actually produces anexception with NS_ERROR_FILE_CORRUPTED in the console output:

In this case, re-running the commands again worked and resolved the issue.

Over time I’ve switched between stable to Developer Edition and eventually toNightly, and I also actively use tools to block cross-domain resources,trackers and so forth. I haven’t looked into the specifics because the issueis so sporadic and now easily solved, but I may if the issues persist.

Ns_error_file_corrupted Firefox

Go Top

Ns Error File Corrupted

Please enable JavaScript to view the comments powered by Disqus.comments powered by Disqus