Firefox 技術支援討論區

After some time of idle, i.e. leave the computer for some time, say over night. No suspend or hibernate. Back to the computer next morning, unlock. Then Firefox appears frozen/hang, can't switch tab (clicking tab has no response, but not really frozen, sometimes responses after dozens of seconds of lag), page also has no response. Then after around half to 2 minutes, everything back to normal.

During the "hang", CPU load is load, no memory stress (swapping/paging).

Environment:

Firefox 123.0 (64-bit), (actually it bothered me for years)

Linux 6.6.15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.15-2 (2024-02-04) x86_64 GNU/Linux

``` lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux trixie/sid Release: n/a Codename: trixie ``` Not related to particular Linux and/or kernel version.

CPU: Intel or AMD, not related. RAM: 64GB/96GB, free memory more than enough.

I will gather more detailed info later.

Hello, have been scratching my head for a while on this one. Have a freshly setup install of Debian 12, using Sway (wayland) as my Window Manager. I am really struggling with slowness in Firefox, page loads take easily 15 seconds whereas loading the exact same page in another window at the same time with Chromium Debian build has near instantaneous load times. I've tried the following troubleshooting steps: - Created a new firefox profile - Tried "Troubleshooting Mode" in Firefox - Disabled ipv6 in firefox about:config and in Debian - Tried different DNS servers - Tried different non-debian specific builds of Firefox - Tried Firefox Beta and Firefox Nightly for Debian

None of these steps made any difference, and Chromium has continued to be significantly faster. Am really stuck here and would love to get to the bottom of this as Firefox is the only browser that works with a HiDPI display in Sway without blurryness. Happy to provide any and all diagnostics and reports that are needed. Thanks in advance!

EDIT: It seems to be some kind of networking issue, using a VPN solves it. But still doesn't explain why Chromium would behave differently.