1869412 - Very slow startup

Status: RESOLVED WORKSFORME

(Core :: Networking: DNS, defect)

Description

[sergio.a.losilla]

Attachment: firefox_binary_crash.log

Steps to reproduce:

1. Start firefox (either from desktop launcher, console, -safe-mode, or -ProfileManager)

Actual results:

Firefox (or the new window) takes very long (~minutes) to appear. Performance is normal after that.

Expected results:

Firefox starts more or less immediately.

Comment 1

[sergio.a.losilla]

Originally reported on Fedora's bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=2252283

According to the maintainer, it looks like Firefox freezes in DNS resolving.

Comment 2

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

This bug was moved into the Performance component.

:sergio.a.losilla, could you make sure the following information is on this bug?

• For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
• For memory usage issues, capture a memory dump from about:memory and attach it to this bug.
• Troubleshooting information: Go to about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.

If the requested information is already in the bug, please confirm it is recent.

Thank you.

Comment 3

[Bas Schouten (:bas.schouten)]

Tentatively moving to network because of the indication that this is related to DNS resolution.

The Performance Impact Calculator has determined this bug's performance impact to be low. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.

Platforms: Windows
Impact on browser: Causes noticeable startup delay
Websites affected: Rare

Comment 4

[Sunil Mayya]

Hello Martin, Sergio
(In reply to sergio.a.losilla from comment #1)

Originally reported on Fedora's bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=2252283

According to the maintainer, it looks like Firefox freezes in DNS resolving.

Do you still observe this issue?

Comment 5

[sergio.a.losilla]

My apologies for not having replied earlier.

The issue seems to have disappeared :-)

Comment 6

[Randell Jesup [:jesup] (needinfo me)]

Thanks! If it happens again, please re-open this bug (or file a new one). It's possible some DoH fixes might have resolved this.