1873371 - Cannot browse on Windows 11, until minutes from boot

Status: RESOLVED WORKSFORME

(Core :: Security: PSM, defect)

Description

[twain43]

Attachment: mozlog obtained via about:logging, zipped

Steps to reproduce:

Updated to Firefox 120+ (issue persists from FF 120 onwards to 121, I just tried to update and had to roll back), both on MacOS Monterey 12.7.2 and Windows 11 (latest 12/2023 update).

I am familiar with the possibility of issues with plugins and extensions, so I also tried a clean install, backupping and deleting all my Profile folders on both systems.
I disabled any proxy, HTTPS only and safe DNS settings, to pin down any possible issue related to misconfigurations. No luck.

Rolling back to Firefox 119.0.1 (clean or with -force-downgrade option for Profile recovery) works fine on both platforms.

This is a "gemini" bugreport, for the MacOS (solved) part, see bug 1871011 .

Actial results:

Firefox starts fine, but cannot connect to ANY website at all.

Depending on the system, the following happens:

On MacOS, the issue was investigated and solved in bug 1871011. Described as follows: "Building certificate chains (at startup, no less) is slow. Using the policy APIs to determine if an enterprise certificate is a trusted root or an intermediate should be faster."

On Windows 11, firefox cannot connect to any website at all, until a few minutes pass.
I am attaching a mozlog generated via ff 121 on Windows.

Expected results:

Browsing the web without issues.

Comment 1

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

The Bugbug bot thinks this bug should belong to the 'Core::Security: PSM' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Dana Keeler (she/her) (use needinfo) [:keeler]]

Thanks! Could you gather a new log but with timestamp,sync,pipnss:4 instead?

Comment 3

[twain43]

Attachment: new mozlog with "timestamp,sync,pipnss:4" options

Comment 4

[twain43]

(In reply to Dana Keeler (she/her) (use needinfo) (:keeler for reviews) from comment #2)

Thanks! Could you gather a new log but with timestamp,sync,pipnss:4 instead?

Sure thing. Here it is. Something must, however, have happened in background: now the browser seems to connect instantly, search me why...

Comment 5

[Dana Keeler (she/her) (use needinfo) [:keeler]]

Thanks! Unfortunately, it seems like the beginning of the log file is cut off. Perhaps trying following the directions at https://firefox-source-docs.mozilla.org/networking/http/logging.html#logging-http-activity-by-manually-setting-environment-variables. Also, if it's not slow anymore, we're unlikely to figure out what the issue was. Is it slow in a new profile? Is it slow if you restart your computer?

Comment 6

[twain43]

(In reply to Dana Keeler (she/her) (use needinfo) (:keeler for reviews) from comment #5)

Thanks! Unfortunately, it seems like the beginning of the log file is cut off. Perhaps trying following the directions at https://firefox-source-docs.mozilla.org/networking/http/logging.html#logging-http-activity-by-manually-setting-environment-variables. Also, if it's not slow anymore, we're unlikely to figure out what the issue was. Is it slow in a new profile? Is it slow if you restart your computer?

I am uploading a new version of the log, made as requested: now it should be complete.
As far as I understand, nothing has changed in my config (or version) so far, no clean or new profile...everything...in any case, I tried restarting firefox and the PC, with no apparent result.

Comment 7

[twain43]

Attachment: new complete mozlog

Comment 8

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

The severity field is not set for this bug.
:keeler, could you have a look please?

For more information, please visit BugBot documentation.

Comment 9

[Dana Keeler (she/her) (use needinfo) [:keeler]]

Unfortunately, that log still doesn't cover the relevant time period. In any case, since the bug isn't reproducible any longer, I'm going to close this as works for me for now. Please re-open this if you can reproduce the bug again. Thanks!