1905517 - Crash in [@ glib_log_writer_func]

Status: NEW

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

Description

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

Crash report: https://crash-stats.mozilla.org/report/index/c8efe8e4-27b3-44e5-80aa-9734b0240624

Reason: SIGTRAP / SI_KERNEL

Top 10 frames of crashing thread:

0  libglib-2.0.so.0  g_log_writer_default  glib/gmessages.c:2827
1  libxul.so  glib_log_writer_func  toolkit/xre/nsSigHandlers.cpp:210
2  libglib-2.0.so.0  g_log_structured_array  glib/gmessages.c:1973
2  libglib-2.0.so.0  g_log_structured_array  glib/gmessages.c:1946
3  libglib-2.0.so.0  g_log_structured_standard  glib/gmessages.c:2030
4  libgdk-3.so.0  _gdk_x11_display_error_event  /build/gtk+3.0-hoOKox/gtk+3.0-3.24.33/gdk/x11/gdkdisplay-x11.c:2766
4  libgdk-3.so.0  _gdk_x11_display_error_event  /build/gtk+3.0-hoOKox/gtk+3.0-3.24.33/gdk/x11/gdkdisplay-x11.c:2711
4  libgdk-3.so.0  gdk_x_error  /build/gtk+3.0-hoOKox/gtk+3.0-3.24.33/gdk/x11/gdkmain-x11.c:296
4  libgdk-3.so.0  gdk_x_error  /build/gtk+3.0-hoOKox/gtk+3.0-3.24.33/gdk/x11/gdkmain-x11.c:258
5  libX11.so.6  _XError  /build/libx11-u5gazC/libx11-1.7.5/src/XlibInt.c:1503

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:

• First crash report: 2024-06-24
• Process type: Parent
• Is startup crash: No
• Has user comments: No
• Is null crash: Yes - all crashes happened on null or near null memory address

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

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

The bug is linked to a topcrash signature, which matches the following criterion:

• Top 5 desktop browser crashes on Linux on release

For more information, please visit BugBot documentation.

Comment 3

[Thinker Li [:sinker]]

glib_log_writer_func should catch crashes. However, it misses this case. I see there is some flags in glib that can turn a non-fatal message to a fatal message. It is probably related to user's configuration or environment. I will dig into it later. However, I don't think it is firefox's fault. We just need to catch the message and crash or exit in a proper way.

Comment 4

[Martin Stránský [:stransky] (ni? me) (PTO till June 6)]

This is just misread error. On the example above the real crash reason is _XError/gdk_x_error and that's fatal. So it's Firefox bug (perhaps).

Comment 5

[Martin Stránský [:stransky] (ni? me) (PTO till June 6)]

Random crash reports:

https://crash-stats.mozilla.org/report/index/19fef8a0-eebf-4ecb-8eef-22f650260416
https://crash-stats.mozilla.org/report/index/19fef8a0-eebf-4ecb-8eef-22f650260416

they're related to D&D - we perhaps deleted D&D window before D&D is finished so we're getting X error.
Wayland counterpart for it should be fixed by https://bugzilla.mozilla.org/show_bug.cgi?id=2025329

This may be as well a Gtk3 bug.

Comment 6

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

The bug is linked to a topcrash signature, which matches the following criteria:

• Top 20 desktop browser crashes on release (startup)
• Top 5 desktop browser crashes on Linux on release (startup)

For more information, please visit BugBot documentation.

Comment 7

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

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit BugBot documentation.