Closed
Bug 1513572
Opened 4 years ago
Closed 4 years ago
Firefox crashes when you merge titlebar and tab list
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox64 | --- | wontfix |
firefox65 | --- | wontfix |
firefox66 | - | wontfix |
People
(Reporter: greatBigDot, Assigned: stransky)
References
(Blocks 1 open bug, )
Details
(Keywords: crash, regression, topcrash-linux)
Crash Data
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0 Steps to reproduce: On Arch Linux with the XFCE4 window manager, simply go to the customization menu (Menu > Customize) and uncheck the "Title Bar" option. Actual results: Firefox immediately crashes. When reopened, the changes to the option in question are not saved. Expected results: Firefox should merge the tab bar and the titlebar, exactly how it did in v-63. Preferably, it would do this without immediately crashing.
Reporter | ||
Updated•4 years ago
|
Blocks: gtktitlebar
Keywords: crash
Reporter | ||
Updated•4 years ago
|
Crash Signature: libglib-2.0.so.0.5800.1@0x5a9b6
Updated•4 years ago
|
Crash Signature: libglib-2.0.so.0.5800.1@0x5a9b6 → [@ libglib-2.0.so.0.5800.1@0x5a9b6 ]
status-firefox64:
--- → affected
status-firefox-esr60:
--- → unaffected
Component: Untriaged → Widget: Gtk
Keywords: regression
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86_64
Updated•4 years ago
|
status-firefox65:
--- → affected
status-firefox66:
--- → affected
Comment 1•4 years ago
|
||
greatBigDot, can you share any Submitted Crash Report IDs listed in your about:crashes page?
Reporter | ||
Comment 2•4 years ago
|
||
Here are the ones from today. Some were in Safe Mode, some with the window maximized/restored, and basically anything else I could think of, in various combinations. Nothing changed the behavior: bp-82fa74dd-909d-41da-a5c8-4c6190181212 bp-3de7b9c6-b6eb-4de4-8ed2-f97090181212 bp-04600591-d1a2-4a27-a741-8989a0181212 bp-cb214812-fc44-4607-a9bc-b7d2e0181212 bp-b3f856f8-547a-407e-9640-3314c0181212 bp-ed976ee1-ad5b-4f81-86a5-7f7620181212 bp-bbb71ab3-04e6-4a9c-8c3c-4390a0181212 bp-a4797a57-bce9-44fb-92fb-ef30f0181212 bp-8daff906-4eb1-45c4-a846-ba1cc0181212 bp-16984324-20db-4427-9152-897b00181212 bp-ac6bba8f-e7b6-4d2b-b64f-3a02c0181212 bp-65fcf76d-738d-41e4-b83b-a6c4c0181212 bp-29d11bfe-55fd-44e1-865c-274f10181212 bp-7464a100-3c86-49de-8b92-c615a0181212 bp-096946ea-9129-4c62-9499-b2fd10181212 bp-8cbdfb4a-e1cf-4bd4-a931-82b000181212 bp-b4f67b35-609d-4694-a1ca-8c5e40181212 Sorry there are so many redundancies; I wasn't really thinking and just clicked through the crash dialogue basically every time, even if the setup was identical to a previous crash.
Comment 3•4 years ago
|
||
I experienced the same issue and found that I could work around it by downgrading gtk3 3.24.1+155+g4c8fcd6a6f-1 to gtk3 3.24.1+8+g220f77d8c1-1. I hope that's of some use in trouble-shooting this.
Reporter | ||
Comment 4•4 years ago
|
||
Downgrading gtk3 worked for me too. Thanks @martinking! Note: I said in the original post that the issue appeared after upgrading to v-64. While true, after downgrading back to v-63, the problem remained for me (even though I had no problems on v-63.0.3 yesterday). Apparently the Firefox update was completely coincidental... I'm not sure. Anyways, downgrading gtk3 makes it work on the current Firefox.
Updated•4 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 5•4 years ago
|
||
Martin is is a bug that falls into your team bucket?
Flags: needinfo?(stransky)
Can confirm, after upgrading firefox it could not start even in safe mode. Arch Linux x86_64, XFCE. I had no issues before, had to refresh firefox to be able to launch it and as soon as I tried to remove the title bar it crashed every time: https://crash-stats.mozilla.com/report/index/af1ed27c-35cb-4238-894a-297240181212 https://crash-stats.mozilla.com/report/index/49c4c8e9-b3bc-46c6-aa4c-388c20181212 https://crash-stats.mozilla.com/report/index/a4cc5b88-f465-4517-867e-97bb50181212 So upon reading your comments the real culprit is gtk3 upgrade and firefox has nothing to do with it?
Comment 7•4 years ago
|
||
This does appear to have been an issue with gtk3 and looks to have been fixed with the upgrade of gtk-update-icon-cache 3.24.1+155+g4c8fcd6a6f-1 -> 3.24.2+1+g2905fc861a-1 on Arch. I'm not a developer so no team bucket. I signed up just to add the gtk3 information. Please let me know if it's not appropriate for me to be posting here and thanks for your help.
Comment 8•4 years ago
|
||
[Tracking Requested - why for this release]: This is the top crash on Linux for the 12-14 Nightly, with 43% of all Linux crashes.
tracking-firefox66:
--- → ?
Keywords: topcrash-linux
Assignee | ||
Comment 9•4 years ago
|
||
(In reply to Pascal Chevrel:pascalc from comment #5) > Martin is is a bug that falls into your team bucket? Yes I'll look at it.
Assignee: nobody → stransky
Assignee | ||
Comment 10•4 years ago
|
||
Can anyone reproduce that on something else than Arch Linux? I tried XFCE on Fedora, both accelerated/non-accelerated windows without any luck. I have the gtk-update-icon-cache-3.24.1 package installed. Link to Arch report: https://bugs.archlinux.org/task/61050 so looks like Arch specific and already fixed there.
Flags: needinfo?(stransky)
Comment 11•4 years ago
|
||
Closing based on the Arch Linux report.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•