1740800 - Deprecated Intel DDX driver: Firefox 94.0 crashes when creating new normal or private window. (Caused by manually enabling blocklisted HW WR.)

Status: RESOLVED FIXED

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

Description

[Peter Sanchez]

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

Steps to reproduce:

Open Firefox
Press "ctrl+shift+p"

(also ctrl+n, also using menu)

Actual results:

Firefox completely crashes. I have submitted some crashes. For example:

https://crash-stats.mozilla.org/report/index/8952479c-7015-48c0-b8e2-542f70211111

Expected results:

A new [private] window should have opened.

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 revert this change in case you think the bot is wrong.

Comment 2

[Darkspirit]

Thanks for the report!
Which desktop environment are you using? (Gnome/KDE/XFCE/etc)
Do you know if you have compositing enabled?
Does Firefox also crash when hovering toolbar icons?

Hardware rendering is disabled by default for your setup because you are using the deprecated Intel DDX driver.
That's when $ xrandr --listproviders contains "Intel" instead of the default and recommended "modesetting".
Some users manually choose this driver to use a legacy in-driver compositor to prevent tearing. It's recommended to use a regular X11 compositor instead. If the performance of uncomposited X11 is desired with a compositor, Wayland is recommended.
Please remove deprecated Driver "intel" from your custom Xorg config file and reboot. Does the crash still occur afterwards?

Comment 3

[Peter Sanchez]

(In reply to Darkspirit from comment #2)

Thanks for the report!
Which desktop environment are you using? (Gnome/KDE/XFCE/etc)

i3-gaps

Does Firefox also crash when hovering toolbar icons?

No

Hardware rendering is disabled by default for your setup because you are using the deprecated Intel DDX driver.
That's when $ xrandr --listproviders contains "Intel" instead of the default and recommended "modesetting".
Some users manually choose this driver to use a legacy in-driver compositor to prevent tearing. It's recommended to use a regular X11 compositor instead. If the performance of uncomposited X11 is desired with a compositor, Wayland is recommended.
Please remove deprecated Driver "intel" from your custom Xorg config file and reboot. Does the crash still occur afterwards?

Thank you! This seems to have been the issue. Simply removing the intel driver and restarting X resolved it. Now I can open new windows (including private) without issue.

Comment 4

[Darkspirit]

(In reply to Peter Sanchez from comment #3)

Thank you! This seems to have been the issue. Simply removing the intel driver and restarting X resolved it. Now I can open new windows (including private) without issue.

To get some certainty: Is it still fixed? Are you able to trigger the crash again if you switch back to the deprecated Intel driver for a short test?

Comment 5

[Peter Sanchez]

(In reply to Darkspirit from comment #4)

To get some certainty: Is it still fixed? Are you able to trigger the crash again if you switch back to the deprecated Intel driver for a short test?

I had already removed the module from the system but I just reinstalled it and yes it did crash again creating a new window.

Comment 6

[Darkspirit]

Thanks for the explicit confirmation!

Fixed by bug 1710400 which disabled HW WR by default for the deprecated Intel DDX driver.

Comment 8

[Darkspirit]

(frederik.elwert from bug 1742663 comment 5)

libEGL warning: DRI2: failed to authenticate

(frederik.elwert from bug 1742663 comment 0)

(firefox:141689): Gdk-ERROR **: 18:46:38.586: The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 3405 error_code 9 request_code 154 (DRI2) minor_code 8)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

(Peter Molnar from bug 1716114 comment 6)

(firefox:341579): Gdk-ERROR **: 15:42:54.795: The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 2710 error_code 9 request_code 154 (DRI2) minor_code 8)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)