1882624 - Firefox refuses to connect to some websites

Status: RESOLVED INCOMPLETE

(Core :: Storage: IndexedDB, defect)

Description

[nullpointeracception]

Attachment: fastmail screenshot

I ran into the same issue after upgrading from an ESR (I think 115) to 123.0.

In the older version, sites had been working perfectly find for months. After I re-opened Firefox, some tabs (mostly my pinned ones interestingly) wouldn't load anymore. I also tried to open them in a non-pinned tab, that didn't help

A few sites that had issues:

• https://app.fastmail.com/mail/Inbox
• https://web.telegram.org/
• https://web.whatsapp.com/
• https://www.phind.com/search

Either the page would stay blank (or very minimal) and not change anymore, or it would reload endlessly (Fastmail). I attached screenshots & console logs.

---

Things I already tried:

1. “Hard” reloading
2. Restart in troubleshooting mode
3. Deleting all cookies and data
4. Unregistering all service workers that had to do with the affected sites (https://mzl.la/3vUgvnd)
5. Going to https://firefox-storage-test.glitch.me but it keeps loading and stays white (also no console output)
6. Deleting matching folders in storage/default/…
7. Deleting SiteSecurityServiceState.bin that only had 2 lines about Fasstmail in it, as far as I can tell.
8. Deleting serviceworker.txt. It only had a single '9' char in it.

Since this was a version upgrade that happened from one minute to the next, it shouldn't be the paths; because those don't change, do they?

Comment 1

[nullpointeracception]

Attachment: phind screenshot

Comment 2

[nullpointeracception]

Attachment: telegram screenshot

Comment 3

[nullpointeracception]

Attachment: whatsapp screenshot

Comment 4

[nullpointeracception]

Attachment: fastmail.log

Comment 5

[nullpointeracception]

Attachment: phind.log

Comment 6

[nullpointeracception]

Attachment: telegram.log

Comment 7

[nullpointeracception]

Attachment: whatsapp.log

Comment 8

[nullpointeracception]

Attachment: troubleshoot-info.json

Comment 9

[nullpointeracception]

After a very long time, while working on this report, the Firefox Storage Test came back and this report tab vanished.

Debug Info:


storage.estimate() threw: Internal error while estimating storage usage
Failed to create "persistent" IDB.
Failed to create "transient" IDB.

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

Comment 10

[nullpointeracception]

Attachment: storage-test.png

Comment 11

[nullpointeracception]

Attachment: storage-test.log

Comment 12

[nullpointeracception]

I kept a tar of the profile state around as it was before I went in to delete stuff.

Comment 13

[nullpointeracception]

Possibly related?

Comment 14

[Kagami Rosylight [:saschanaz] (they/them)]

Do you see any log when you:

1. In F12 Devtools, click 3-dot button
2. Under Advanced settings, "Enable remote debugging" and "Enable browser chrome and add-on debugging toolboxes"
3. Open browser toolbox via Firefox app menu ➡️ More tools ➡️ Browser toolbox
4. See the console

Failing to run storage.estimate sounds like a DB malfunctioning, but let's see.

Comment 15

[nullpointeracception]

It does not show much:

Given tab is not restoring. SessionStore.sys.mjs:6821:15
Failed to send a WebChannel message. No currentWindowGlobal. WebChannel.sys.mjs:218:17
<Provider> does not support changing `store` on the fly. It is most likely that you see this error because you updated to Redux 2.x and React Redux 2.x which no longer hot reload reducers automatically. See https://github.com/reactjs/react-redux/releases/tag/v2.0.0 for the migration instructions. react-redux.js:881:13
The resource at “https://googleads.g.doubleclick.net/adsid/google/si?gadsid=AORoGNQ3LO5SE2OuN1GdZ0HWcN-vLzF7nJQ4XiEstxCUk9mpaWxPi2cIiQ” was blocked by OpaqueResponseBlocking. Reason: “nosniff is true and mimeType is an opaque-blocklisted MIME type or its essence is 'text/plain'”.
IndexedDB UnknownErr: ActorsParent.cpp:556

But I think the regular console output when opening https://web.telegram.org/k/ is more. Attaching a new log file.

Comment 16

[nullpointeracception]

Attachment: telegram2.log

Comment 17

[Kagami Rosylight [:saschanaz] (they/them)]

Certainly it's not just SW but something more core thing is totally broken. Let's say storage for now.

Comment 18

[Andrew Sutherland [:asuth] (he/him)]

Something is definitely broken with your profile. Thanks for the details of your diagnostic attempts in comment 0 and the details from comment 15.

I would suggest, with Firefox not running, delete the following from your profile directory:

• serviceworker.txt
• storage.sqlite - this is the metadata about the contents of the QuotaManager-managed storage/ directory.
• the storage/ subdirectory. While the targeted removals from comment 0 were a good approach, it seems like there must be some kind of lingering problem in the directory tree which is having side effects.

In theory, more information should have been visible in the browser console (which the steps from comment 14 should also expose, although the remote debugging stuff/browser toolbox was not strictly necessary), but since you already tried to get that data in comment 15, it likely makes sense to just go directly to the steps above. One note is that the browser console is a circular buffer and potentially useful messages might have disappeared by the time you looked, especially if session restore was loading a lot of content tabs.

Setting needinfo so I can know if that fixes things for you.

Comment 19

[BugBot [:suhaib / :marco/ :calixte]]

A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Given that the bug is still UNCONFIRMED, closing the bug as incomplete.

For more information, please visit BugBot documentation.