After update to version 95 on Ubuntu 14.04 LTS, firefox freezes when I close any window (SW WR/Unity X11)
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox95 | --- | wontfix |
| firefox96 | --- | wontfix |
| firefox97 | --- | wontfix |
| firefox98 | --- | wontfix |
People
(Reporter: alberto.pires.on, Unassigned)
References
(Regression)
Details
(Keywords: crash, hang, regression)
Crash Data
Attachments
(4 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36
Steps to reproduce:
I was running version 94.02 and upgraded to version 95, after that it started to freeze every time I try to close a window or the firefox itself.
I fresh install of firefox 95 had the same result.
I'm running on Ubuntu Linux 14.04 LTS
Actual results:
After closing any window, for example the help window or the firefox itself the all windows become unresponsive and the GekoMain process starts running in loop consuming 100% of cpu, the only way out is to kill the process.
It seems to be happening only with pop-up windows or the main window itself, for example, if I click on the help menu and try to close the help window it freezes, or when I try to login into a site using my google credentials, it opens a pop-up for me to select the account and when it try to close it freezes.
Closing tabs seems ok, so far.
The problem happened on two different Ubuntu 14.04 machines, in 16.04 it worked.
Expected results:
To be able to just close the window.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•3 years ago
|
||
Thanks for the report! Please open about:support in your address bar, click on "Copy text to clipboard" and paste it here.
| Reporter | ||
Comment 3•3 years ago
|
||
| Reporter | ||
Comment 4•3 years ago
|
||
| Reporter | ||
Comment 5•3 years ago
|
||
Comment on attachment 9254242 [details]
"Raw data" (JSON File)
I've also included the raw data just in case
Comment 6•3 years ago
|
||
Can you please use mozregression tool to find the broken commit?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks!
| Reporter | ||
Comment 7•3 years ago
|
||
I'm having a hard time installing mozregression_tool, but meanwhile I tested some beta versions and found out that
it broke on 95.0b3 - build (20211104185958). On 95.0b2 and below it works.
I hope it helps.
I give it another try on the mozregression tool.
| Reporter | ||
Comment 8•3 years ago
|
||
Comment 9•3 years ago
•
|
||
$ sudo apt-get install python3-pip
$ pip3 install --user mozregression
$ ~/.local/bin/mozregression --good 93 --bad 96
Comment 10•3 years ago
|
||
(alberto.pires.on from comment #7)
I'm having a hard time installing mozregression_tool, but meanwhile I tested some beta versions and found out that
it broke on 95.0b3 - build (20211104185958). On 95.0b2 and below it works.
That would be: https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=FIREFOX_95_0b2_RELEASE&tochange=FIREFOX_95_0b3_RELEASE
| Reporter | ||
Comment 11•3 years ago
|
||
Output from mozregression:
18:53.05 INFO: Using local file: /tmp/tmpf5keko_f/ea923d92b6ad-pgo--autoland--target.tar.bz2 (downloaded in background)
18:53.05 INFO: Running autoland build built on 2021-11-01 10:24:54.466000, revision ea923d92
19:07.65 INFO: Launching /tmp/tmphyh2lrd4/firefox/firefox
19:07.65 INFO: Application command: /tmp/tmphyh2lrd4/firefox/firefox -profile /tmp/tmpyrx3iogw.mozrunner
19:07.66 INFO: application_buildid: 20211101101141
19:07.66 INFO: application_changeset: ea923d92b6ad88935b76c5f314d5bb9b15d54d84
19:07.66 INFO: application_name: Firefox
19:07.66 INFO: application_repository: https://hg.mozilla.org/integration/autoland
19:07.66 INFO: application_version: 95.0a1
Was this integration build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', 'back' or 'exit' and press Enter): bad
19:40.61 INFO: Narrowed integration regression window from [770627d2, 2f9fee41] (3 builds) to [770627d2, ea923d92] (2 builds) (~1 steps left)
19:40.61 INFO: No more integration revisions, bisection finished.
19:40.61 INFO: Last good revision: 770627d2ad0778d82c9df06dc44b9e93cc985ada
19:40.61 INFO: First bad revision: ea923d92b6ad88935b76c5f314d5bb9b15d54d84
19:40.61 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=770627d2ad0778d82c9df06dc44b9e93cc985ada&tochange=ea923d92b6ad88935b76c5f314d5bb9b15d54d84
Comment 12•3 years ago
|
||
ea923d92b6ad88935b76c5f314d5bb9b15d54d84 stransky — Bug 1736949 [Linux] Implement child popup windows support, r=emilio
Updated•3 years ago
|
Comment 13•3 years ago
|
||
Can you test latest nightly?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binaries
Thanks.
Comment 14•3 years ago
|
||
If you can reproduce it with nightly, please try to provide crash ID per:
https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Getting_Mozilla_crash_report_from_running_application
Thanks.
| Reporter | ||
Comment 15•3 years ago
|
||
I could reproduce the crash, the id is bp-a3de95d9-113e-41c4-bbde-553000211209
https://crash-stats.mozilla.org/report/index/a3de95d9-113e-41c4-bbde-553000211209
Updated•3 years ago
|
Updated•3 years ago
|
Comment 16•3 years ago
•
|
||
(In reply to alberto.pires.on from comment #15)
Does this crash/hang still occur with latest Nightly?
(bug 1750017 has been fixed)
| Reporter | ||
Comment 17•3 years ago
|
||
Yes, I've just tested on firefox-98.0a1.en-US.linux-x86_64 and it still hangs, then I need to kill it.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 18•3 years ago
|
||
Hm, I can't build Firefox there and also I'm unable to install gtk3 debug symbols so I'm unable to do anything there.
Updated•3 years ago
|
Comment 19•3 years ago
|
||
The bug has a crash signature, thus the bug will be considered confirmed.
Comment 20•3 years ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•