1743569 - Crash in [@ handle_response | _XEventsQueued] - frequency increase starting with 96.0a1

Status: RESOLVED WORKSFORME

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

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

This signature got more frequent for Nightly on 2021-11-09 (there is one build from 2021-11-05 which also reported several crashes). Release doesn't show the uptick.

All crashes for the last week used AMD graphic cards.

Crash report: https://crash-stats.mozilla.org/report/index/6ff9e8b8-4ba2-405c-ad87-86dd60211130

Reason: SIGTRAP

Top 10 frames of crashing thread:

0 libglib-2.0.so.0 _g_log_abort 
1 libglib-2.0.so.0 g_log_writer_default glib/gmessages.c:2694
2 libglib-2.0.so.0 g_log_structured_array glib/gmessages.c:1898
3 libglib-2.0.so.0 g_log_structured_standard glib/gmessages.c:1982
4 libgdk-3.so.0 _gdk_x11_display_error_event ../../../../../gdk/x11/gdkdisplay-x11.c:2763
5 libgdk-3.so.0 gdk_x_error ../../../../../gdk/x11/gdkmain-x11.c:269
6 libX11.so.6 _XError src/XlibInt.c:1491
7 libX11.so.6 handle_error src/xcb_io.c:199
8 libX11.so.6 handle_response src/xcb_io.c:324
9 libX11.so.6 _XEventsQueued src/xcb_io.c:344

Comment 1

[Darkspirit]

Since Bug 1743821, a known BadWindow xShape crash (bug 1730991) now occurs even without GPU process and without Nvidia: bug 1750017

Comment 2

[Darkspirit]

bug 1741956, bug 1743551, bug 1743386 might also be related.

Comment 3

[Gabriele Svelto [:gsvelto] (PTO)]

FYI lots of crashes in the release channels have comments mentioning they were watching or interacting with YouTube videos at the time of crash. There was also this comment which might be relevant:

the stdout/stderror on the terminal session for the main Firefox process ended with: (firefox:56998): Gdk-ERROR **: 16:15:37.012: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadIDChoice (invalid resource ID chosen for this connection)'. (Details: serial 159345268 error_code 14 request_code 138 (XFIXES) minor_code 5) (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.)

The same users also mentions this:

When the crash happened I was using another application and all Firefox windows were in the background/hidden, so user interaction does not appear to have been the immediate trigger.

Comment 4

[furkan_bugzilla]

Attachment: log

In case this is relevant: I have been experiencing this error approximately once per day (sometimes more often) since updating to Ubuntu 21.10 (and it has continued since updating to Ubuntu 22.04). One major change in Ubuntu 21.10 was that Firefox began being distributed as a snap instead of an apt package.

This is what I see in the systemd journal after the crash occurs:

Comment 5

[furkan_bugzilla]

A few more points, to clarify:

1. By "this error" I was referring to the error in Comment #3 above:
   The program 'firefox' received an X Window System error.
   This probably reflects a bug in the program.
   The error was 'BadIDChoice'.
   (Details: serial 53739949 error_code 14 request_code 138 (XFIXES) minor_code 5)

2. I experience the same behaviour on two of my systems. My newer system had a fresh install of Ubuntu 21.10 (later upgraded to 22.04). But my older system was upgraded from Ubuntu 21.04 to 21.10 and that is when I started experiencing the error. I have been using the older system since 2018 (I originally had installed Ubuntu 18.04 on it and updated it with each successive release) and I have never previously encountered this behaviour pattern. Both systems have a Radeon GPU (I mention that in case this is graphics-related).

3. I also experience the same behaviour pointed out in the last quote from Comment 3: "When the crash happened I was using another application and all Firefox windows were in the background/hidden, so user interaction does not appear to have been the immediate trigger."

For me it sometimes happens while I am using the browser, and sometimes also happens when I'm working on something else and I notice either in my application dock or on the secondary screen that my Firefox windows have all disappeared.

Comment 6

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

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Comment 7

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

Closing because no crashes reported for 12 weeks.