I noticed this morning that TBPL wasn't loading. When I opened the web console and tried again I found this error: NS_ERROR_FILE_CORRUPTED: File error: Corrupted The line that it happened on is: if (!("mostRecentlyUsedTrees" in storage) || I also noticed that Tweetdeck wasn't working, and it has a similar error: NS_ERROR_FILE_CORRUPTED: Component returned failure code: 0x8052000b (NS_ERROR_FILE_CORRUPTED) [nsIDOMStorage.getItem] Its JS is minified, so I can't pull the source for it. The simple workaround here is to clear my local storage out, but this seems like a pretty bad state to get into. Is there anything we can do to help apps cope with this better, or do they need to be catching some existing exceptions or such?

I'm getting the NS_ERROR_FILE_CORRUPTED for sites that, according to the Developer Toolbar, don't have local storage. As with the duplicate bug, this happens to me with feedly; it also happens to me with travis-ci.org and connect.garmin.com. There is nothing under the storage directory in my profile obviously relating to any of the these sites. If there is any further information I can provide, please let me know

For the devtools case, I think the problem is that localstorage starts returning errors permanently once it encounters a localstorage problem on behalf of any origin. (All localstorage data is stored in the same database, which leads to this problem.) Duping forward to bug 1341070 where I've written some stuff.