Firefox Freezes But Websites Don't
Categories
(Core :: Performance: General, defect)
Tracking
()
| Performance Impact | pending-needinfo |
People
(Reporter: mohemiv, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0
Steps to reproduce:
When I start Firefox, everything functions normally.
Then, after a different period of time, from 1 hour to several days, Firefox freezes. Only Firefox controls freeze, namely tabs and menus. The website that was opened in the current tab is functioning normally.
Sometimes, you can switch a tab to a different website. Sometimes, you can't do it.
Sometimes, after 1-2 minutes everything returns to normal. Sometimes you have to restart the browser.
No warnings no exceptions no logs.
|
||
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
|
||
Comment 2•1 year ago
|
||
This bug was moved into the Performance component.
:mohemiv, 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:memoryand 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•1 year ago
|
||
Hi! Just a reminder, this note from bugbot is the key one here that would help us understand what's going wrong:
- For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
Please give that a try, if you can manage to capture the issue in the profiler. (You might need to just leave the profiler running for a while until the issue happens.)
|
|
||
Updated•1 year ago
|
I'm trying. Unfortunately, after the freeze, I was never able to press the Profiler button. It never worked. No reaction from UI whatsoever. Also, for the last 2-3 days there has been no freeze :(
|
|
||
Comment 5•1 year ago
•
|
||
Thanks. Yeah, if it locks up indefinitely, the profiler can't help you because you never get an opportunity to capture the profile, as you observed.
In that case, your best bet is to kill firefox (when it's hanging) with kill -11 [pid] (where [pid] is the numeric pid for the firefox parent process, which you might find in top or from this command:
ps aux --sort pid | grep firefox | head
(Second column of output should be the PID there.)
If you run that kill -11 command and give it the Firefox parent-process PID, it will kill Firefox in a way that gives you a Mozilla crash reporter dialog. If you submit a crash report, then you can visit about:crashes later on and you'll see a link to your crash report listed there, and you can share the URL of it here. That crash report should help us find out what code Firefox is stuck in, when it's hanging.
|
|
||
Comment 7•1 year ago
•
|
||
Thanks. That crash report looks like "everything's working fine" to me at first glance (we're just waiting for input, not deadlocking or hanging anywhere). So that's slightly perplexing.
There is one slight clue in the "Crash Annotations" section which is:
|[0][GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt (t=22314)
...which suggests that some graphics code experienced a rendering failure at 6 hours (22,314s) after startup. But that was a long time before the crash report was generated (which was 4+ days after startup). So it's unlikely that this particular rendering failure-warning was unrelated to the issue, but it might be a hint about other sorts of rendering failures that might be periodically happening.
A performance profile would still really be useful if it were possible to capture -- and given that Firefox is just failing to paint but not necessarily pegged, I suspect you can capture a profile using the key-combo rather than the (unclickable) button. You should be able to start profiling with Ctrl+Shift+1, and then capture with Ctrl+Shift+2.
Would you mind trying that? (double-check that the Ctrl+Shift+1 / Ctrl+Shift+2 key combinations work on your end -- and if they do, just leave firefox profiling and then capture a profile with Ctrl+Shift+2 after the issue happens -- hopefully that'll successfully open a new tab, where you can click "upload local file" at the top right of the web page, and then the web UI will show you a short-URL that hopefully you can copypaste.)
(Assuming that works, you may want to share the profile link privately via email [e.g. to me at dholbert at mozilla dot com] rather than here on the bug, depending on how comfortable you are with posting the domains you're visiting & tiny-screenshots of some of them -- those may be present in the profile, depending on which boxes you check in the profile-upload dialog.)
|
||
Comment 8•1 year ago
|
||
Hi mohemiv - if you're still experiencing this, can you try what dholbert suggests in comment 7 to generate a performance profile?
Hi! For some reason, the bug hasn't occurred in the last 9 days, even though I'm still using the same system configuration. Before this, the bug appeared 2-3 times a day. I will monitor the behavior of the browser for another month and try to catch the bug.
|
||
Comment 10•1 year ago
|
||
Hi mohemic, resolving this for now as you're reported that you can't reproduce it anymore! Please re-open and include a profile if you see this issue again! Thanks!
Description
•