Closed Bug 1867035 Opened 2 years ago Closed 2 years ago

Some users are experiencing a persistent startup delay after Firefox 120 update

Categories

(Core :: Storage: Quota Manager, defect)

Product:
Core
Component:
Storage: Quota Manager
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1867095
Tracking Flags:
Tracking Status
firefox120 --- fixed
firefox121 --- fixed
firefox122 --- fixed

People

(Reporter: yannis, Unassigned)

References

Details

There are many reports from users experiencing slowness after updating to Firefox 120, as seen on Reddit (1, 2, 3, 4, 5). Most reports talk about a startup delay of 5 to 15 seconds, followed by normal behavior. Some users mention that clearing cookie and site data fixed the issue for them. Some users mention that disabling all addons fixes the issue for them, but that enabling any addon brings it back. One user has shared a profile that suggests a link with storage. The profile looks rather similar to bug 1778472. We wonder if bug 1865098 might be related. At the moment we don't have enough information about the affected population to make good progress. I will reach the users and ask them to provide more information in this bug if possible.

Edit: Added a new Reddit thread.

If you are affected by this issue, please respond here with as much information as you can provide. In particular, all of the following would be helpful for our investigation:

  • Describe precisely how Firefox behaves in your case. Is it a delay only at startup, or every time you load a page? Do the pages get loaded in the end, or do they continue trying to load forever? Did it occur with previous versions of Firefox?
  • Mention your platform (e.g. Windows 11) and region (e.g. Europe/France). Mention any antivirus software you are using.
  • Share the contents of about:support as an attachment (copy the raw contents to clipboard, then paste it in a new file named about-support.json).
  • Share a link to a performance profile where you reproduce the issue. You can start Firefox with the environment variable MOZ_PROFILER_STARTUP=1 to create a startup performance profile, which would be even better.
  • Does disabling all your addons (temporarily just for the test) make the issue disappear?
  • If you navigate to about:profiles and open the root folder for the current profile, what is the total size of the storage folder? How many files does it contain? (On Windows, this information can be seen with right click, Properties.) Then under storage/default, there should be one folder per website. Can you identify which website has the folder with the most files and/or taking the biggest size on disk? (On Windows you can use WinDirStat for that, on Linux you can use Disk Usage Analyzer.) What is the size, and the number of files? Can you share the name of the website? Is it a website that you visit often? Is it pinned? If you navigate to about:preferences#privacy and clear the site data for this specific website, does it make the issue go away?
  • If you navigate to about:serviceworkers, how many entries are listed?

Edit: Added question related to service workers based on comment 11.

I'm experiencing this issue.

  • My Firefox (version 120.0) is set to load to a blank new tab. The application opens as normal, but when I click to load ANY web page then there'll be a 10 to 12 second delay before those tabs load in. The delay seems to begin from "opening the application" not from "clicking the tabs" so if I waited 8 seconds before clicking to open a tab, the delay to open will be shorter. If I click to open a new tab immediately on Firefox start, the delay will be 10-12 seconds.

  • I am running Firefox version 120.0 and Windows 10 Home (10.0.19045 Build 19045)

  • Performance Profile - https://share.firefox.dev/3uBUmw4

  • Disabling my extensions DOES solve the problem. However re-enabling ANY extension brings it back again. I can't trace the problem to any one extension.

  • Profile storage folder size is 953mb on disk, containing 36,962 files.

  • Largest single website folder is https+++teams.live.com (99.91mb), second largest is https+++mail.google.com (94.52mb)

When i boot up my pc when i come home and opens firefox, then it takes like 10 seconds to load my start page that is google it self.
Then its very slow to load any site. Sometimes even images takes for ever to load like a old dial up modem. This happens everyday when i power up my pc from cold start.

using 120. 0 64 bit version with 3 addons only: Ublock and newtap and useragent.
I tryed disable these but its the same.

Im using win 10 pro 64 bit full updated. Eu

i dont know how to share profile...

.558 MB in that folder
18.879 files.

We also need to know if the slowdown is observable after each subsequent startup or only after the first startup when FF has been upgraded to FF 120.

(In reply to Jan Varga [:janv] from comment #4)

We also need to know if the slowdown is observable after each subsequent startup or only after the first startup when FF has been upgraded to FF 120.

It happens with every startup of Firefox, not just the first startup after update.

My company is having this issue as well.

Firefox 120 (no add-ons) on Windows 10/11. Website takes 5-15 seconds to respond, after which the site works normally. If a subsequent request (say AJAX...we have many) the process starts over.

So far I've only noticed the issue with our internal entrprise sites. This setup has been working fine until employees began updating to FF120.

The setup we have been using before FF120 is as follows: We distribute our enterprise root certificate to Windows machines via Group Policy (manually installed them for MacOS) then manually enable "security.enterprise_roots.enabled" in Firefox config.

Our current workaround is to visit the workstation and manually import our enterprise root certificate directly into Firefox using Settings->View Certificates->Import. After this things work normally.

(In reply to thammer from comment #6)

My company is having this issue as well.

Firefox 120 (no add-ons) on Windows 10/11. Website takes 5-15 seconds to respond, after which the site works normally. If a subsequent request (say AJAX...we have many) the process starts over.

So far I've only noticed the issue with our internal entrprise sites. This setup has been working fine until employees began updating to FF120.

The setup we have been using before FF120 is as follows: We distribute our enterprise root certificate to Windows machines via Group Policy (manually installed them for MacOS) then manually enable "security.enterprise_roots.enabled" in Firefox config.

Our current workaround is to visit the workstation and manually import our enterprise root certificate directly into Firefox using Settings->View Certificates->Import. After this things work normally.

I should point out that I tested a Windows 11 workstation (in Parallels) using FF119 first to ensure things are working as they should. I then upgraded to FF120 and the problem manifested. I should also point out that other browsers (Chrome, Edge) worked fine with our internal secure sites. Only FF120 exhibits the issue and only on our internal secure sites. I also want to mention that once the site loads, the security indicators on the URL bar appear as they should (encryption enabled). It's just the 5 to 15 second delay that's causing the issues.

My experience with v120 is intermittent. Startup is usually "normal", though occasionally might extend to ~5 seconds, but not anything that's made me take note.

The issue that I'm experiencing is frequently, but not always, domain lookup will take a very long time, sometimes 30 seconds or more. Other times, and it's not anything that I've been able to reliably reproduce to capture on performance profiler, is the UI will completely lockup, and be unresponsive for 15-20 seconds. Disabling DOH had a slight improvement on the domain lookup, as it no long performed the TLS handshake, but UI still intermittently locks up.

I've tried starting the profile capture when this occurs, but the button doesn't work until the UI starts responding again. This is new behavior in this version of Firefox. Disabling extensions did not seem to have an impact on the issue.

Win11, 32gb ram, 5900x, 6900XT
US/Eastern, MS Defender
Profile Storage is 7.37GB, with 31.348 files and 15,120 folders. Largest folder is Youtube because of how Youtube Premium "downloads" save videos.

(In reply to Jan Varga [:janv] from comment #4)

We also need to know if the slowdown is observable after each subsequent startup or only after the first startup when FF has been upgraded to FF 120.

As for the slowdown caused by Quota Manager, it occurs every time the browser is restarted when pages that have a large number of files in the morgue folder have been opened in the previous browsing session. In my case open.spotify.com has 14k+ files and the next in line are two sites 3.5k+ and 1k+. After opening these 3 pages and blank.org, closing Firefox and restarting the browser from the command line: & 'C:\Program Files\Mozilla Firefox\firefox.exe' 'https://blank.org' the Quota Manager thread spends 6772ms in EnsureTemporaryStorageIsInitialized. In LoadQuota 6735ms, in InitializeOrigin 6695ms, in mozilla::dom::cache::CacheQuotaClient::InitOrigin 6597ms,and finally in mozilla::dom::cache::BodyTraverseFiles::::operator() 6247ms. Only here, after a few lambdas, we have two functions sharing this time to a significant extent: mozilla::dom::quota::GetDirEntryKind and mozilla::dom::cache::(anonymous namespace)::GetBodyUsage::::operator()::::operator() 4579ms and 1533ms. Both functions boil down under Windows to multiple calls to GetFileAttributesW and GetFileAttributesExW, respectively. So the problem is already identified in https://bugzilla.mozilla.org/show_bug.cgi?id=1866240. If Firefox does not have to check every file in the morgue at each startup the delay at startup will not depend on the number of files to be processed in the morgue folders.

link to profiler data: https://share.firefox.dev/3Gl33xl

Piotr, thanks for pointing that out. We know about that and it will be addressed in bug 1866240 (there are also other ideas for Cache API and we will be filing new bugs for that).
However, there's something else which made things worse overall in FF 120 and it's being fixed in bug 1867095.

Follow up to my issue, I had a large number of service workers listed on about:serviceworkers. I didn't count, but it was a couple hundred at least. I unregistered every one that was there, and since doing that, I haven't experienced any of the issues. Still a little early to definitively say it worked, but since doing that I haven't had a single lockup or excessive page load time.

Long page load time was back today. Experienced on both my work computer, which is a M2 Pro Mac and my home windows computer. I was able to capture the performance profile from the win computer.

https://share.firefox.dev/3GlTIFp

Thanks everyone!

(In reply to averyalex from comment #2)

(In reply to jeff.delamater from comment #12)

https://share.firefox.dev/3GlTIFp

These two profiles match with the profile we already had available. Your comments motivated the work in bug 1867095, which we believe should fix your issue in Firefox 120.0.1, which is currently being shipped. Please report back to let us know if that is indeed fixed for you two.

(In reply to Psycrow from comment #3)

Then its very slow to load any site. Sometimes even images takes for ever to load like a old dial up modem.

This doesn't seem to match with the issue that other users were experiencing, so unfortunately I don't expect that Firefox 120.0.1 will solve your problem. It would be interesting for us if you could record a performance profile as explained here. Did you try to follow the steps? Can you explain where you are stuck?

(In reply to thammer from comment #6)

Firefox 120 (no add-ons) on Windows 10/11. Website takes 5-15 seconds to respond, after which the site works normally. If a subsequent request (say AJAX...we have many) the process starts over.

So far I've only noticed the issue with our internal entrprise sites. This setup has been working fine until employees began updating to FF120.

The setup we have been using before FF120 is as follows: We distribute our enterprise root certificate to Windows machines via Group Policy (manually installed them for MacOS) then manually enable "security.enterprise_roots.enabled" in Firefox config.

Our current workaround is to visit the workstation and manually import our enterprise root certificate directly into Firefox using Settings->View Certificates->Import. After this things work normally.

This also doesn't seem to match with the issue that other users were experiencing, so I don't expect that Firefox 120.0.1 will solve your problem either. Would it be possible for you to record a performance profile as explained here so that we can get a better idea of what's going on?

(In reply to Yannis Juglaret [:yannis] from comment #15)

(In reply to thammer from comment #6)

Firefox 120 (no add-ons) on Windows 10/11. Website takes 5-15 seconds to respond, after which the site works normally. If a subsequent request (say AJAX...we have many) the process starts over.

So far I've only noticed the issue with our internal entrprise sites. This setup has been working fine until employees began updating to FF120.

The setup we have been using before FF120 is as follows: We distribute our enterprise root certificate to Windows machines via Group Policy (manually installed them for MacOS) then manually enable "security.enterprise_roots.enabled" in Firefox config.

Our current workaround is to visit the workstation and manually import our enterprise root certificate directly into Firefox using Settings->View Certificates->Import. After this things work normally.

This also doesn't seem to match with the issue that other users were experiencing, so I don't expect that Firefox 120.0.1 will solve your problem either. Would it be possible for you to record a performance profile as explained here so that we can get a better idea of what's going on?

I confirmed that our enterprise root certificate doesn't appear in the list when I go to Settings->Privacy & Security->Certificates->View Certificates. I made sure that "Allow Firefox to automatically trust third-party root certificates you install" was checked. I also verified that our enterprise root certificate was installed properly via certmgr.msc->Certificates->Trusted Root Certificate Authorities->Certificates. Then I ran the profiler and uploaded it as requested: https://share.firefox.dev/47UsrpA

(In reply to thammer from comment #16)

(In reply to Yannis Juglaret [:yannis] from comment #15)

(In reply to thammer from comment #6)

Firefox 120 (no add-ons) on Windows 10/11. Website takes 5-15 seconds to respond, after which the site works normally. If a subsequent request (say AJAX...we have many) the process starts over.

So far I've only noticed the issue with our internal entrprise sites. This setup has been working fine until employees began updating to FF120.

The setup we have been using before FF120 is as follows: We distribute our enterprise root certificate to Windows machines via Group Policy (manually installed them for MacOS) then manually enable "security.enterprise_roots.enabled" in Firefox config.

Our current workaround is to visit the workstation and manually import our enterprise root certificate directly into Firefox using Settings->View Certificates->Import. After this things work normally.

This also doesn't seem to match with the issue that other users were experiencing, so I don't expect that Firefox 120.0.1 will solve your problem either. Would it be possible for you to record a performance profile as explained here so that we can get a better idea of what's going on?

I confirmed that our enterprise root certificate doesn't appear in the list when I go to Settings->Privacy & Security->Certificates->View Certificates. I made sure that "Allow Firefox to automatically trust third-party root certificates you install" was checked. I also verified that our enterprise root certificate was installed properly via certmgr.msc->Certificates->Trusted Root Certificate Authorities->Certificates. Then I ran the profiler and uploaded it as requested: https://share.firefox.dev/47UsrpA

I also noticed that my Firefox version had auto-updated to 120.0.1 and the problem still happens

(In reply to Yannis Juglaret [:yannis] from comment #13)

Thanks everyone!

(In reply to averyalex from comment #2)

(In reply to jeff.delamater from comment #12)

https://share.firefox.dev/3GlTIFp

These two profiles match with the profile we already had available. Your comments motivated the work in bug 1867095, which we believe should fix your issue in Firefox 120.0.1, which is currently being shipped. Please report back to let us know if that is indeed fixed for you two.

I've been using 120.0.1 for several hours now, and haven't experienced the issues I was experiencing before. Seems like for me, this update has addressed the problem.

When I encountered the slowdowns after updating, i wiped everything and reinstalled and that fixed the problem. The recommended firefox wipe didn't do it for me though, I had to deep clean every file

(In reply to jeff.delamater from comment #18)

(In reply to Yannis Juglaret [:yannis] from comment #13)

Thanks everyone!

(In reply to averyalex from comment #2)

(In reply to jeff.delamater from comment #12)

https://share.firefox.dev/3GlTIFp

These two profiles match with the profile we already had available. Your comments motivated the work in bug 1867095, which we believe should fix your issue in Firefox 120.0.1, which is currently being shipped. Please report back to let us know if that is indeed fixed for you two.

I've been using 120.0.1 for several hours now, and haven't experienced the issues I was experiencing before. Seems like for me, this update has addressed the problem.

Seconding this, everything seems "back to normal" for me too.

Thank you!

(In reply to thammer from comment #16)

I made sure that "Allow Firefox to automatically trust third-party root certificates you install" was checked. I also verified that our enterprise root certificate was installed properly via certmgr.msc->Certificates->Trusted Root Certificate Authorities->Certificates. Then I ran the profiler and uploaded it as requested: https://share.firefox.dev/47UsrpA

Thanks for the performance profile. I filed bug 1867794, where people working on network should be able to help you more. Please refer to this other bug for further investigation of your issue.

Status: NEW → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1867095
Resolution: --- → DUPLICATE
No longer depends on: 1867794
See Also: → 1867794

(In reply to Jan Varga [:janv] from comment #10)

Piotr, thanks for pointing that out. We know about that and it will be addressed in bug 1866240 (there are also other ideas for Cache API and we will be filing new bugs for that).

Piotr, bug 1866240 is now fixed and the telemetry shows quite significant improvements. Do you happen to use Nightly and eventually share your experience after the fix ?

Flags: needinfo?(piotrborkowski)

(In reply to Jan Varga [:janv] from comment #23)

(In reply to Jan Varga [:janv] from comment #10)

Piotr, thanks for pointing that out. We know about that and it will be addressed in bug 1866240 (there are also other ideas for Cache API and we will be filing new bugs for that).

Piotr, bug 1866240 is now fixed and the telemetry shows quite significant improvements. Do you happen to use Nightly and eventually share your experience after the fix ?

I don't normally use nightly, but I installed it, copied the profile(before running nightly I removed any sync settings from prefs.js and the signedInUser.json file so that two browsers don't sync with the same guid) and tested with pages from 1000 to 19000 files in the dom cache. The difference is huge. In Fx120, QM_QUOTA_INFO_LOAD_TIME_V0 is 7000 to 12000. In Nightly, the worst QM_QUOTA_INFO_LOAD_TIME_V0 result I got was 349 just after system startup and usually it is 190 to 250. So there is practically no delay in loading the startup page after browser startup.

Flags: needinfo?(piotrborkowski)

Piotr, thanks a lot for the confirmation, we appreciate it.

status-firefox120: --- → fixed
status-firefox121: --- → fixed
status-firefox122: --- → fixed
Component: Storage: localStorage & sessionStorage → Storage: Quota Manager
You need to log in before you can comment on or make changes to this bug.