Firefox 107+ freezes and is unresponsive under X11
Categories
(Core :: Widget: Gtk, defect, P2)
Tracking
()
People
(Reporter: calcifer, Unassigned)
References
()
Details
Attachments
(2 files)
+++ This bug was initially created as a clone of Bug #1795574 +++
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0
Steps to reproduce:
Bug #1795574 was incorrectly closed. The original reporter was on X11 (as I am) but the "fix" was for a Wayland regression. The issue happens to me every 5-10 minutes on X11 with the latest Firefox beta.
Original report from #1795574 below:
Unclear to me -- I will just browse the internet normally when the browser suddenly totally freezes. I have not figured out a repeatable trigger.
Actual results:
The browser totally looks up and is unresponsive. I cannot scroll, type, right-click, or interact with the browser in any way (that includes the Firefox chrome, not just the web content).
I then get a "Unresponsive Application" popup from GNOME -- I have tried "waiting" for Firefox to unfreeze, but this does not seem to ever happen (or at least, it did not happen within 1 minute).
Looking at htop, I do not see much CPU usage (in fact, Firefox seems to use almost 0 CPU when this happens).
|
||
Comment 1•2 years ago
|
||
Thanks. Can you:
- Attach about:support page
- Try to get backtrace of the freeze (https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Application_freeze)
- Use mozregression tool to find broken commit (https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool)
Thanks.
|
Reporter | |
Comment 2•2 years ago
|
||
|
|
Reporter | |
Comment 3•2 years ago
|
||
Hopefully, this should cover everything. Please let me know if something else is needed.
I think I'm encountering the same bug. Seeing it in 107 and 102.5.0ESR. Platform is Arch Linux w/ KDE, X11, nvidia GPU. Whatever bug I am experiencing, the problematic code seems to have been backported. It's also possible this isn't a bug at all with firefox, but with some other desktop component or toolkit it uses...
I am suspecting it is related to highlighting text (which I do compulsively, a la XKCD 1271, lol...). The last few times I've seen it happen I had just highlighted something... or maybe it happened when I clicked again to unhighlight...
@can are you also on arch linux? Guessing based on your kernel in about:support.
|
|
Reporter | |
Comment 5•2 years ago
|
||
@rocky yes, we are in the same situation. Arch Linux, Nvidia, X11, compulsive text highlighting.
I wonder if this is not really a Firefox issue, but a bug with pango because I've noticed a similar (though not exactly the same) situation over there [1].
(In reply to Can from comment #5)
@rocky yes, we are in the same situation. Arch Linux, Nvidia, X11, compulsive text highlighting.
I wonder if this is not really a Firefox issue, but a bug with pango because I've noticed a similar (though not exactly the same) situation over there [1].
I don't think this is the issue. I don't recall having this issue a month ago, which was the last time it was updated on my system.
I'm gonna downgrade my system to the packages on November 1st (using archive.archlinux.org) to see if the problem goes away, and do a binary search to find the date that it broke. Then we can figure out what packages were updated then to narrow down the cause.
I'm not 100% sure when it started. If you know when it started for you, let me know, it might speed up the process.
This link isn't working for me.
Also same issue here, on Manjaro/X11/Nvidia. Firefox freezes sometimes on highlight and when opening new window (I think).
For me happened first time yesterday(16th), and downgrading firefox to previous working version 106.0.2 didn't seemed to help.
Maybe found something helpful:
journalctl -b had this at the time of freeze:
Nov 17 13:54:30 pc kernel: firefox[899986]: segfault at d8 ip 00007f25c1428814 sp 00007fffd1fab358 error 4 in libX11.so.6.4.0[7f25c141900>
libx11 was upgraded bit before the issue started.
Downgraded libx11 to libx11-1.8.1-3 from 1.8.2-1 and so far haven't gotten any freezes(for few hours on semi active use, would have previously crashed few times in this time).
Though can't yet be sure it wasn't just a coincidence, and I have been just lucky with avoiding freezes.
(In reply to sauce47 from comment #7)
libx11 was upgraded bit before the issue started.
Downgraded libx11 to libx11-1.8.1-3 from 1.8.2-1 and so far haven't gotten any freezes(for few hours on semi active use, would have previously crashed few times in this time).
Same, I see an update from/to the same versions of libx11 in my pacman logs, November 14th. I'll test that on my system too, thanks.
Turns out that update hit arch on the 12th. So I'll try my system updated to the 11th for a few hours, then update and see if it breaks.
Full list of packages updated between the 11th and 12th (on my system at least):
bluez-5.66-1 bluez-libs-5.66-1 bluez-utils-5.66-1 grantlee-5.3.1-1 iana-etc-20221107-1 libx11-1.8.2-1 python-setuptools-1:65.1.1-1
The only package the is updated between those dates that I could see having any bearing on this is libx11...
Also interesting, I see a pkgrel bump to libx11 recently, only enabling debug, lol. I would not be surprised if it were related to this.
https://github.com/archlinux/svntogit-packages/commit/ee643c9a1a995f6f4aa11acf996d84601accf602
|
||
Comment 10•2 years ago
|
||
@sauce47 I think you're right about that libx11 package. I think I've reproduced your observations. I downgraded my entire system to archlinux's state as of the 11th. Then I upgraded libx11 to 1.8.2-1 and observed a freeze. Next I downgraded to 1.8.1, and have been using it for a little while without freezing.
In any case, this doesn't look like a firefox bug. I opened a bug with libx11 here: https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/168
|
|
||
Comment 11•2 years ago
|
||
Pretty sure I found the problematic commit, see the issue on freedesktop.org above.
|
|
||
Comment 12•2 years ago
|
||
(In reply to Can:calcifer from comment #3)
Created attachment 9303744 [details]
gdb.txtHopefully, this should cover everything. Please let me know if something else is needed.
It looks like deadlock in clipboard code. Async clipboard should fix that - Bug 1778201.
|
|
||
Comment 13•2 years ago
|
||
Gyus, can you test latest Mozilla binaries if that fixes it?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries
Thanks.
|
|
||
Comment 14•2 years ago
|
||
Also if you see the crashes in Firefox 107 (and former version works), please use mozregreesion tool to find broken commit:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.
|
|
||
Comment 15•2 years ago
|
||
Ah, I missed the comment 10. If it's X11 bug there's no need to test Mozilla binaries.
|
|
Reporter | |
Comment 16•2 years ago
|
||
(In reply to Martin Stránský [:stransky] (ni? me) from comment #14)
Also if you see the crashes in Firefox 107 (and former version works), please use mozregreesion tool to find broken commit:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.
107 also crashes. It could just be a libx11 bug, or perhaps it's an issue with both Firefox and libx11. I haven't been able to reproduce it since reverting the commit in [1].
[1] https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/168
|
|
||
Comment 17•2 years ago
|
||
Thanks for testing. May be also caused by sync clipboard on FF side, we really need to implement the async one.
|
||
Comment 19•2 years ago
|
||
ran into this on 109.0a1 (2022-11-19) (and probably earlier versions as well). Installing libx11-git (libx11-1.8.2.r3.ga9e84580-1), and it still crashes in different ways, without freezes though. Here's a crash report I was able to get: https://crash-stats.mozilla.org/report/index/8889cfbd-c7fc-4a9a-9409-48adf0221123
|
|
||
Comment 20•2 years ago
|
||
And another one, this time for sure because of pasting: https://crash-stats.mozilla.org/report/index/7c43a694-d689-44c3-afb6-645c00221123
|
|
||
Comment 21•2 years ago
|
||
Dupe of Bug 1781167?
|
|
||
Updated•2 years ago
|
|
||
Updated•2 years ago
|
|
||
Comment 24•2 years ago
|
||
(Can:calcifer from comment #16)
I haven't been able to reproduce it since reverting the commit in [1].
[1] https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/168
|
|
||
Updated•2 years ago
|
Description
•