1811034 - [X11/KDE] Fedora 37 Firefox 108 crashes regularly when adding a another word to the already entered search string on Google

Status: UNCONFIRMED

(Core :: Widget: Gtk, defect, P3)

Description

[[e-mail]]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0

Steps to reproduce:

While in google.com or many other sites, adding a new keyword to the already entered search string now crashes firefox for linux fedora 37.
I searched for something google.. then I went back to enter another keyword. It froze then crashed 1 seceond later.

Actual results:

I had launched it from console to see the error, here is what it said:
$ firefox
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Child 10285, Main Thread] WARNING: Call to mmap failed: Cannot allocate memory: file /builddir/build/BUILD/firefox-108.0.1/ipc/chromium/src/base/shared_memory_posix.cc:515
IPDL protocol error: SharedMemory::Map failed
[Parent 9711, IPC I/O Parent] WARNING: process 10285 exited on signal 11: file /builddir/build/BUILD/firefox-108.0.1/ipc/chromium/src/base/process_util_posix.cc:256
^CExiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=77.3392) Exiting due to channel error.

Expected results:

smooth sailing

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Darkspirit]

Thanks for the report!
Please try to find a regression range, you will get a pushlog url at the end:
$ pip3 install mozregression
$ mozregression --good 106 --bad 108 -a https://google.com

If 108 from above command has been fine, the problem might have been backported from 109 to 108, then try this:
$ mozregression --good 106 --bad 109 -a https://google.com

Comment 3

[[e-mail]]

Many thanks.. I just finished the mozregression - I wildly tried many web sites until it crashed or not.. some versions did not crash at all. I marked those as good , and I marked the crashed ones as bad. I hope I did this correctly. Do I need to do anything else?

the last page looked like:
25:37.90 INFO: Narrowed integration regression window from [4053f6c0, 7a43d6de] (6 builds) to [4053f6c0, d254e2dd] (4 builds) (~2 steps left)
25:37.90 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=4053f6c0e941203c00fc50b712be9d6d249f3c14&tochange=d254e2dd277b574fb7299afd7a44d84159a54188

25:37.90 INFO: Using local file: /tmp/tmps6y7pji1/71bdd943e80b--autoland--target.tar.bz2 (downloaded in background)
25:37.90 INFO: Running autoland build built on 2022-09-30 20:10:43.155000, revision 71bdd943
25:49.88 INFO: Launching /tmp/tmpt4p3tlpm/firefox/firefox
25:49.88 INFO: Application command: /tmp/tmpt4p3tlpm/firefox/firefox https://google.com -profile /tmp/tmpjev75q8c.mozrunner
25:49.89 INFO: application_buildid: 20220927215131
25:49.89 INFO: application_changeset: 71bdd943e80b8ac3c391fa133c053eb334c0604a
25:49.89 INFO: application_name: Firefox
25:49.89 INFO: application_repository: https://hg.mozilla.org/integration/autoland
25:49.89 INFO: application_version: 107.0a1
Was this integration build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', 'back' or 'exit' and press Enter): good
28:46.27 INFO: Narrowed integration regression window from [4053f6c0, d254e2dd] (4 builds) to [71bdd943, d254e2dd] (2 builds) (~1 steps left)
28:46.27 INFO: No more integration revisions, bisection finished.
28:46.27 INFO: Last good revision: 71bdd943e80b8ac3c391fa133c053eb334c0604a
28:46.27 INFO: First bad revision: d254e2dd277b574fb7299afd7a44d84159a54188
28:46.27 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=71bdd943e80b8ac3c391fa133c053eb334c0604a&tochange=d254e2dd277b574fb7299afd7a44d84159a54188

Comment 4

[Darkspirit]

Please also open about:support, click on "Copy text to clipboard" and paste it here. Thanks!

Comment 5

[Martin Stránský [:stransky] (ni? me)]

Also can you create a screencast of the issue?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Collect_information_for_a_bug_report
Thanks.

Comment 6

[[e-mail]]

Attachment: requested info

Comment 7

[[e-mail]]

Attachment: gfxlog.txt

Comment 8

[[e-mail]]

]$ sudo rpm -q firefox
firefox-109.0-1.fc37.x86_64

Comment 9

[[e-mail]]

Attachment: simplescreenrecorder-2023-01-19_13.51.07.mkv

Comment 10

[Martin Stránský [:stransky] (ni? me)]

Can you try to get crash backtrace by coredumpctl?
https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Using_coredumpctl_to_get_backtrace
Thanks.

Comment 11

[Martin Stránský [:stransky] (ni? me)]

Also can you attach about:support from Firefox 106 and 105?

Launch it by mozregression as:

mozregression --launch 106
mozregression --launch 105

Thanks.

Comment 12

[[e-mail]]

Attachment: gdb.txt

Comment 13

[[e-mail]]

(In reply to Martin Stránský [:stransky] (ni? me) from comment #10)

Can you try to get crash backtrace by coredumpctl?
https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Using_coredumpctl_to_get_backtrace
Thanks.

sure.. done.. I attached gdb.txt

Comment 14

[[e-mail]]

(In reply to Martin Stránský [:stransky] (ni? me) from comment #11)

Also can you attach about:support from Firefox 106 and 105?

Launch it by mozregression as:

mozregression --launch 106
mozregression --launch 105

Thanks.

I'm sorry that gave an error.. how shall I proceed?

[turgut@tkbiglaptop ~]$ mozregression --launch 106
Traceback (most recent call last):
File "/home/turgut/.local/bin/mozregression", line 5, in <module>
from mozregression.main import main
File "/home/turgut/.local/lib/python3.11/site-packages/mozregression/main.py", line 22, in <module>
from mozregression.cli import cli
File "/home/turgut/.local/lib/python3.11/site-packages/mozregression/cli.py", line 22, in <module>
from mozregression.config import DEFAULT_CONF_FNAME, get_config, write_config
File "/home/turgut/.local/lib/python3.11/site-packages/mozregression/config.py", line 10, in <module>
from configobj import ConfigObj, ParseError
ModuleNotFoundError: No module named 'configobj'
[turgut@tkbiglaptop ~]$ mozregression --launch 105
Traceback (most recent call last):
File "/home/turgut/.local/bin/mozregression", line 5, in <module>
from mozregression.main import main
File "/home/turgut/.local/lib/python3.11/site-packages/mozregression/main.py", line 22, in <module>
from mozregression.cli import cli
File "/home/turgut/.local/lib/python3.11/site-packages/mozregression/cli.py", line 22, in <module>
from mozregression.config import DEFAULT_CONF_FNAME, get_config, write_config
File "/home/turgut/.local/lib/python3.11/site-packages/mozregression/config.py", line 10, in <module>
from configobj import ConfigObj, ParseError
ModuleNotFoundError: No module named 'configobj'
[turgut@tkbiglaptop ~]$

Comment 15

[[e-mail]]

Sorry found my mistake - I'm re-installing mozregression now..

Comment 16

[[e-mail]]

Attachment: Mozregression --launch 106 about:support output

Mozregression --launch 106 about:support output:

Comment 17

[[e-mail]]

Attachment: mozregression --launch 105 about:support output