Closed Bug 1591723 Opened 5 years ago Closed 4 years ago

FF 70 64 bit: facebook and local storage management not working after update

Categories

(Core :: Storage: localStorage & sessionStorage, defect)

70 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: alexander.stern, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

Win 7 64 bit. FF build 70 64 bit.
Updated to build 70

Actual results:

Facebook not working (shows only a top ribbon - works perfectly in other browsers)
Asustor management - not working (shows the options, clicks on any option doesn't achieve anything. Works perfectly in other browsers)

Expected results:

Expected to have no issues after the update to build 70.

  1. Restarted the FF in Safe Mode / no add-ons. Same problem
  2. Disabled the Enhanced Tracking Protection for the facebook. The https://facebook.com is in the Exceptions list now. Same problem.

I'm investigating the issue and I'll send more information soon. https://firefox-storage-test.glitch.me reports "Investigating... If this doesn't go away, things are unexpectedly broken." because even LocalStorage database for that site seems to be corrupted and script.js doesn't handle that currently.
For now, you can can fallback to the old LocalStorage implementation by changing "dom.storage.next_gen" preference to "false".

I have this issue in Linux / Ubuntu. I seem to be able to get in via a private window.

Hi Alex. This should be working properly already, it was fixed 2 weeks ago. Please let us know if you are still having problems with it, if not we will proceed to close the bug. Regards, Flor.

Flags: needinfo?(alexander.stern)

Ubuntu 18.04,
Firefox 70.0.1

I guess it's difficult to fix it if it's not happening on the developers machines. Let me know if there is anything I can provide that can help the debug process.

dom.storage.next_gen is set to the default value of false (toggling it to true didn't help either).
Same issues as a lot of others have reported - can't use trello, facebook, login to google, etc.

https://firefox-storage-test.glitch.me/ says my localStorage is broken.

{
  "v": 1,
  "curVersion": 70,
  "prevVersion": 0,
  "ls": {},
  "qm": {
    "lastWorkedIn": 70
  },
  "idb": {
    "persistentCreatedIn": 0,
    "persistentLastOpenedIn": 70,
    "clearDetectedIn": 0
  },
  "cache": {
    "firstCacheCreatedIn": 0,
    "unpaddedOpaqueCreatedIn": 0,
    "paddedOpaqueCreatedIn": 70
  }
}

Trying to clear localStorage on a crashing site gives the error

>> localStorage.clear()
[Exception... "File error: Corrupted"  nsresult: "0x8052000b (NS_ERROR_FILE_CORRUPTED)"  location: "JS frame :: debugger eval code :: <TOP_LEVEL> :: line 1"  data: no]

While running glitch.io in a private browsing instance it says the Cache API is fullyBroken:

A mutation operation was attempted on a database that did not allow mutations.
The operation is insecure.
{
  "v": 1,
  "curVersion": 70,
  "prevVersion": 70,
  "ls": {},
  "qm": {
    "lastWorkedIn": 70
  },
  "idb": {
    "persistentCreatedIn": 0,
    "persistentLastOpenedIn": 0,
    "clearDetectedIn": 0
  },
  "cache": {
    "firstCacheCreatedIn": 0,
    "unpaddedOpaqueCreatedIn": 0,
    "paddedOpaqueCreatedIn": 0
  }
}

Hi ,

I wasn't able to reproduce the bug but I've chosen a component for this bug in hope that someone with more expertise may look at it. We'll await their answer. If you consider that there's another component that's more proper for this case you may change it.

Regards, Flor.

Component: Untriaged → Storage: localStorage & sessionStorage
Product: Firefox → Core

Hi,

we are investigating a similar (random) behaviour regarding cleared localStorage while browsing from page to page.

Example:

  1. go to idealo.de and click on a product link (https://www.idealo.de/preisvergleich/OffersOfProduct/6073137_-sm5573-10-picobaristo-deluxe-saeco.html)
  2. there are at least 2 localStorage keys with values in idealo.de context
  3. go to a sub domain page of Idealo (account.idealo.de) or any other different web page
  4. switch back to idealo.de start page by using browser back button by direct call
  5. there are no localStorage keys

Unfortunately it happens randomly but we can reproduce it mainly in a private tab/window.

This behaviour happens in Firefox 70, 71 and 72 (stable, dev, nightly build) on Linux and macOS (with and w/o ad blocker)

We are sure that it don't happens if you switch on "next gen storage" in "about:config".

Regards,

Ingo (idealo.de)

A colleague told me today that this happens also on other web pages that rely on certain localStorage keys.

(In reply to ingo.stoecker from comment #7)

Hi,

we are investigating a similar (random) behaviour regarding cleared localStorage while browsing from page to page.

Example:

  1. go to idealo.de and click on a product link (https://www.idealo.de/preisvergleich/OffersOfProduct/6073137_-sm5573-10-picobaristo-deluxe-saeco.html)
  2. there are at least 2 localStorage keys with values in idealo.de context
  3. go to a sub domain page of Idealo (account.idealo.de) or any other different web page
  4. switch back to idealo.de start page by using browser back button by direct call
  5. there are no localStorage keys

Unfortunately it happens randomly but we can reproduce it mainly in a private tab/window.

This behaviour happens in Firefox 70, 71 and 72 (stable, dev, nightly build) on Linux and macOS (with and w/o ad blocker)

We are sure that it don't happens if you switch on "next gen storage" in "about:config".

Regards,

Ingo (idealo.de)

This bug has ended up with several different issues being discussed:

  • Comment 0: This was an instance of QuotaManager being broken and the enabling of LSNG breaking LocalStorage and thereby lots of web sites. This was addressed by the disabling of LSNG on 70 release and general work to correct QM initialization failures is tracked on the meta bug 1482662.
  • Comment 5 is a broken LocalStorage (non-NG) database breaking LocalStorage, which results in similar symptoms from the former but will be addressed by LSNG and can be recovered from by using "Refresh Firefox" from about:support.
  • Comment 7 sounds like bug 1526949 which is about a lack of durability for LocalStorage in PrivateBrowsing mode. Similar problems may be observed when Firefox is operating in SESSION cookie mode when not using LSNG and multiple tabs which are hosted in different processes are in use.

Resolving WORSKFORME since the comment 0 issue was addressed.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(alexander.stern)
Resolution: --- → WORKSFORME

I got FF Developer 73.0b3 (64-bit)

And 3 days a go i updated it and i got this bug then!

So its fixed on normal FF and now we get the bug so when do we get the fix?

Facebook, only loads in safe mode and Speed Dial [FVD] (https://addons.mozilla.org/en-US/firefox/addon/fvd-speed-dial/) plugin stopped working also!

Did i reinstall and its not working still!

(In reply to dawe from comment #10)

I got FF Developer 73.0b3 (64-bit)

Dear :dawe, Firefox Beta and Nightly have LSNG enabled for testing purposes. So there the problem may still occur, as you prove. May I ask you to save the current Firefox profile data of your browser such that we might use it for debugging purposes? After that you might want to follow these instructions in order to disable LSNG. Thank you.

@(In reply to Jens Stutte [:jstutte] from comment #11)

(In reply to dawe from comment #10)

I got FF Developer 73.0b3 (64-bit)

Dear :dawe, Firefox Beta and Nightly have LSNG enabled for testing purposes. So there the problem may still occur, as you prove. May I ask you to save the current Firefox profile data of your browser such that we might use it for debugging purposes? After that you might want to follow these instructions in order to disable LSNG. Thank you.

Thats was already off or false!

Is it anyway way to revert? Like i said i downloaded it again and reinstalled it! BUT still its not working!

You need to log in before you can comment on or make changes to this bug.