NEW 290175
REGRESSION(284894@main?): [GTK] Crash in AccessibilityObjectAtspi::registerObject when opening web inspector
https://bugs.webkit.org/show_bug.cgi?id=290175
Summary REGRESSION(284894@main?): [GTK] Crash in AccessibilityObjectAtspi::registerOb...
davidquinterogranadillo
Reported 2025-03-21 07:23:24 PDT
Created attachment 474668 [details] Page crashes when opening web inspector Technical information: Epiphany (GNOME Web) version: 48.0 WebKitGTK 2.48.0 GStreamer 1.24.12 GTK 4.18.2 Libadwaita 1.7.0 Distributor: GNOME Operating System: Debian GNU/Linux 12 (bookworm) x86_64 Flatpak version: 1.14.10 Whenever I try to inspect a page (any web page), the page crashes (image attached with the crash). Already reported this to GNOME Web, but it was marked as an issue with WebkitGTK: https://gitlab.gnome.org/GNOME/epiphany/-/issues/2613 CLI shows the following text: MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:782: FINISHME: support YUV colorspace with DRM format modifiers MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:814: FINISHME: support more multi-planar formats with DRM modifiers VM 0x7f853d40a000 on pid 2 received NeedDebuggerBreak trap (epiphany:2): epiphany-WARNING **: 00:10:46.346: Web process crashed
Attachments
Page crashes when opening web inspector (133.39 KB, image/png)
2025-03-21 07:23 PDT, davidquinterogranadillo
no flags
Stack trace of the Webkit GTK crash (12.55 KB, text/plain)
2025-03-22 07:51 PDT, davidquinterogranadillo
no flags
Michael Catanzaro
Comment 1 2025-03-21 08:41:53 PDT
Thanks for taking the time to report this issue. Unfortunately, without a stack trace from the crash it's very hard to know what caused it. Please see https://handbook.gnome.org/issues/stack-traces.html for more information on how to provide a stack trace.
davidquinterogranadillo
Comment 2 2025-03-22 07:51:29 PDT
Created attachment 474685 [details] Stack trace of the Webkit GTK crash I followed the instructions for flatpak reporting as noted here: https://handbook.gnome.org/issues/stack-traces.html
davidquinterogranadillo
Comment 3 2025-03-22 07:51:53 PDT
Hello, I just added the stack trace as an attachment
Philippe Normand
Comment 4 2025-03-23 13:25:20 PDT
Looks like an host issue, probably related with misconfigured dbus or a11y. Is this in GNOME or some other desktop session?
davidquinterogranadillo
Comment 5 2025-03-23 13:51:58 PDT
I'm using GNOME 43 running Wayland
Philippe Normand
Comment 6 2025-03-23 14:08:41 PDT
That's the assert, afaict, RELEASE_ASSERT(!m_isConnecting) in AccessibilityAtspi::registerObject(). I cannot reproduce this here on F42 (GNOME).
davidquinterogranadillo
Comment 7 2025-03-23 15:05:45 PDT
Is there anything I can do to help you reproduce the bug?
Radar WebKit Bug Importer
Comment 8 2025-03-24 06:35:59 PDT
Philippe Normand
Comment 9 2025-03-28 10:42:14 PDT
Sorry, I can indeed reproduce this. I'm not very familiar with atspi though, not sure I can help much :(
Philippe Normand
Comment 10 2025-04-12 09:26:45 PDT
Is this still happening David? I cannot reproduce it here anymore, but I think it's a race condition... It looks like AccessibilityAtspi::registerObject() is called before the dbus async name ownership claim completed (m_isConnecting is set to false in AccessibilityAtspi::didOwnName())... Georges, can you take a look please?
Peter Bittner
Comment 11 2025-05-20 12:09:13 PDT
I run WebKitGTK 2.48.2 with GNOME Web 48.3 (GStreamer 1.26.0, GTK 4.18.5, Libadwaita 1.7.2) on NixOS and the issue still occurs. The browser tab crashes both with the Inspector and when browsing regularly. Epiphany logs "Web process crashed" in the terminal when this occurs.
Peter Bittner
Comment 12 2025-05-23 00:21:56 PDT
I might need to withdraw my report above from 3 days ago. I've not seen any crash on the same WebKitGTK 2.48.2 based GNOME Web 48.3 browser anymore.
Philippe Normand
Comment 13 2025-05-23 12:05:35 PDT
It's a flaky crash according to comment 10, so sometimes it will happen and sometimes not.
Note You need to log in before you can comment on or make changes to this bug.