1863047 - Crash in [@ mozilla::widget::WlLogHandler]

Status: REOPENED

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

Description

Crash report: https://crash-stats.mozilla.org/report/index/2c9f3b91-0727-4cad-b6fc-083a60231102

MOZ_CRASH Reason: unknown object (4278190083), message error(ous)

Top 10 frames of crashing thread:

0  libxul.so  MOZ_Crash  mfbt/Assertions.h:281
0  libxul.so  mozilla::widget::WlLogHandler  widget/gtk/nsWaylandDisplay.cpp:179
1  libwayland-client.so.0  wl_log  src/wayland-util.c:430
2  libwayland-client.so.0  wl_display_read_events  src/wayland-client.c:1705
3  libgdk-3.so.0  gdk_event_source_check.lto_priv.0  /build/gtk+3.0-WfzL5N/gtk+3.0-3.24.33/gdk/wayland/gdkeventsource.c:94
4  libglib-2.0.so.0  g_main_context_check  glib/gmain.c:4037
5  libglib-2.0.so.0  g_main_context_iterate  glib/gmain.c:4210
6  libglib-2.0.so.0  g_main_context_iteration  glib/gmain.c:4278
7  libxul.so  nsAppShell::ProcessNextNativeEvent  widget/gtk/nsAppShell.cpp:418
7  libxul.so  nsBaseAppShell::DoProcessNextNativeEvent  widget/nsBaseAppShell.cpp:131

This crash has the comment "Drag and drop PNG image onto Google Drive's File upload screen". There were some older bugs fixed with this signature, but there are still plenty of them on Nightly.

Comment 1

[BugBot [:suhaib / :marco]]

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 2

[BugBot [:suhaib / :marco]]

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

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

For more information, please visit BugBot documentation.

Comment 3

[BugBot [:suhaib / :marco]]

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.

Comment 4

[Manuel Bucher [:manuel]]

This crash has the comment "Drag and drop PNG image onto Google Drive's File upload screen". There were some older bugs fixed with this signature, but there are still plenty of them on Nightly.

I can confirm, my crash was also when drag&drop a png into Element Chat on chat.mozilla.org. But I cant reproduce. The crash happened on the second time I drag&dropped the same png.

Comment 5

[Manuel Bucher [:manuel]]

In debug mode I get persistent MOZ_ASSERTS when dragging&dropping files into Firefox.
Pernosco with a few comments in the notebook on what is happening: https://pernos.co/debug/SSIaEjKXhPFDjgvnRyeMJA/index.html
It seems like a bad timestamp is coming from drag_drop_event_cb: https://docs.gtk.org/gtk3/vfunc.Widget.drag_drop.html

Comment 6

[Liz Henry (:lizzard)]

Maybe related to bug 1897115, the fix for which landed in 128 nightly and 127 beta 5.

Comment 7

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

This crash reproduces in a Ubuntu 24.04 VM since it got set up - with recent Firefox releases since April. Dragging a file from the file manager into a Google Drive folder in the browser causes the crash. The cursor flickers over the GDrive pane, unknown if related.

Comment 8

[Ivar Hill]

I am getting this crash signature on Fedora Silverblue 40 after having updated my Nvidia GPU drivers. Curiously, it does not seem to relate - at least not exclusively - to drag and drop behavior. Rather, Firefox crashes within seconds to about a minute from starting, every time, regardless of what I do. If I disable hardware acceleration, it no longer crashes - so it seems GPU-related in some regard.

I'm on GNOME and Wayland - more details here: https://crash-stats.mozilla.org/report/index/a9271cbc-4425-4874-973b-3ba630240706#tab-details

Comment 9

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

(In reply to Ivar Hill from comment #8)

I am getting this crash signature on Fedora Silverblue 40 after having updated my Nvidia GPU drivers. Curiously, it does not seem to relate - at least not exclusively - to drag and drop behavior. Rather, Firefox crashes within seconds to about a minute from starting, every time, regardless of what I do. If I disable hardware acceleration, it no longer crashes - so it seems GPU-related in some regard.

I'm on GNOME and Wayland - more details here: https://crash-stats.mozilla.org/report/index/a9271cbc-4425-4874-973b-3ba630240706#tab-details

That's Bug 1898476.

Comment 10

[Mayank Bansal]

Bug 1909172 appears to have a way to reproduce a crash that has the same signature.

Comment 11

[flymon]

I can reproduce this crash on my Ubuntu 22.04 machine about 20% of the time on both firefox and thunderbird just by drag and dropping files from nautilus. Firefox is installed through snap, thunderbird through apt. On firefox didn't matter what website I was on when drag and dropping, both gmail and jira crashed. On thunderbird i just click "new message" and keep dragging files until it inevitably crashes. I keep losing work because of the crashes so if you need more info please contact me.

https://crash-stats.mozilla.org/report/index/d0797217-4aef-48e2-a8a6-4c6040240725

Comment 12

[Wayne Mery (:wsmwk)]

#1 crash for Thunderbird 128.*esr and 128.0b, and therefore extremely important.
But oddly enough not #1 crash for 129.0b

Comment 13

[Wayne Mery (:wsmwk)]

(In reply to Wayne Mery (:wsmwk) from comment #12)

#1 crash for Thunderbird 128.*esr and 128.0b, and therefore extremely important.

Thunderbird are virtually all flatpak

Comment 15

[Wayne Mery (:wsmwk)]

See comment 11. Can you reproduce?

Comment 16

[Wayne Mery (:wsmwk)]

bbhtt, amanita, Do you have nvidia?

Comment 17

[bbhtt]

Nope, AMD.

Comment 18

[Amanita]

no, amd back then, now intel

Comment 19

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

mozilla::widget::WlLogHandler() is just a Wayland error log handler and there are various reason why we crash. The recent spike (1k crashes) looks related to Bug 1908825 which looks like caused by new egl-wayland-1.1.14 library update. Downgrade to egl-wayland-1.1.13 fixes it according to reports and that's also reason why flatpak works.

Comment 20

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

Hello,

I have tried to reproduce this issue using Ubuntu 22 and Ubuntu 24 with Intel Chipset, as well as Ubuntu 24 on a VM(M2 chipset) but was unable to reproduce it using 128.1.0esr(20240730200333), 128.0esr(20240710185639), 128.0b6(20240701153450) and 130.0a1(20240804065331).

Comment 21

[Corey Bryant]

Vlad, It may also be worth testing on a different distro than Ubuntu to recreate. The current development version of Ubuntu has egl-wayland-1.1.13: https://launchpad.net/ubuntu/+source/egl-wayland

Comment 22

[flymon]

(In reply to flymon from comment #11)

I can reproduce this crash on my Ubuntu 22.04 machine about 20% of the time on both firefox and thunderbird just by drag and dropping files from nautilus. Firefox is installed through snap, thunderbird through apt. On firefox didn't matter what website I was on when drag and dropping, both gmail and jira crashed. On thunderbird i just click "new message" and keep dragging files until it inevitably crashes. I keep losing work because of the crashes so if you need more info please contact me.

https://crash-stats.mozilla.org/report/index/d0797217-4aef-48e2-a8a6-4c6040240725

Hey, reporting back. I updated other packages yesterday and can't reproduce the crash in firefox nor thunderbird anymore. I'm not sure which of the packages fixed it for me but ones that could be relevant were xserver, linux-firmware and ubuntu-desktop. I can post the full list if needed. Firefox is still on 128.0.3, same version that was crashing before.

Comment 23

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

Hello,

I tried once again on Ubuntu 24 and made sure that I have Wayland version egl-wayland-1.1.13 with GNOME , updated my nvidia drivers to 560.28.0 with egl-wayland 1.1.14 and still was unable to reproduce it.

I also tried reproducing this crash on Fedora SilverBlue 40(VM) and Fedora Workstation 40(VM) as well as the top crasher Freedesktop SDK 23.08 (VM) but was unable to reproduce.

Comment 24

[Thomas Pasch]

For me, it looks like https://bugzilla.mozilla.org/show_bug.cgi?id=1908825 is related

Comment 25

[Daniel Darnell [:dandarnell]]

I was able to replicate this crash with Ubuntu 24 on a VM (running on Intel hardware) using the latest stable Thunderbird Flatpak. It does appear to be caused by egl-wayland (libnvidia-egl-wayland1), as far as I can tell from the crash report.

The latest version (v1.1.15) appears to have fixed the explicit sync crash that is affecting Thunderbird and Firefox. Assuming this crash is related to bug 1908825, as Thomas mentioned, then v1.1.15 of egl-wayland should fix this bug too.

Comment 26

[Thomas Pasch]

On my Fedora 40 (desktop) system, with egl-wayland 1.1.15, nvidia akmods version 560.31.02 and firefox from getfirefox.net version 129.0.1, I still encounter crashes but substantial less frequent:

bp-8cf6629c-cb12-49a7-aec3-4b7640240814 14.08.24, 10:20

Installed Packages
Name : egl-wayland
Version : 1.1.15
Release : 1.fc40
Architecture : x86_64
Size : 83 k
Source : egl-wayland-1.1.15-1.fc40.src.rpm
Repository : @System
From repo : fedora-multimedia
Summary : EGLStream-based Wayland external platform
URL : https://github.com/NVIDIA/egl-wayland
License : MIT
Description : EGL External Platform library to add client-side Wayland support to EGL on top
: of EGLDevice and EGLStream families of extensions.
:
: This library implements an EGL External Platform interface to work along with
: EGL drivers that support the external platform mechanism.

Comment 27

[Thomas Pasch]

On my Fedora 40 (desktop) system, egl-wayland has been updated to another 1.1.15 version (sic!).
With nvidia akmods version 560.31.02 and firefox from getfirefox.net version 129.0.1, I still encounter crashes but substantial less frequent:

bp-d7e63fc4-e72c-4407-8a57-bec990240817 17.08.24, 14:11
bp-094791d6-ebfe-4592-a669-6ecae0240817 17.08.24, 14:11

Installed Packages
Name : egl-wayland
Version : 1.1.15
Release : 2.20240814gitf30cb0e.fc40
Architektur : x86_64

Comment 28

[Thomas Pasch]

More crashes:

bp-91352c03-adfc-4dd2-8f88-a5bbc0240819 19.08.24, 10:02
bp-429b493c-e913-4768-bc88-ea54c0240819 19.08.24, 09:56

I think https://bugzilla.mozilla.org/show_bug.cgi?id=1909162 is related.

Comment 29

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

(In reply to Thomas Pasch from comment #27)

On my Fedora 40 (desktop) system, egl-wayland has been updated to another 1.1.15 version (sic!).
With nvidia akmods version 560.31.02 and firefox from getfirefox.net version 129.0.1, I still encounter crashes but substantial less frequent:

bp-d7e63fc4-e72c-4407-8a57-bec990240817 17.08.24, 14:11
bp-094791d6-ebfe-4592-a669-6ecae0240817 17.08.24, 14:11

Installed Packages
Name : egl-wayland
Version : 1.1.15
Release : 2.20240814gitf30cb0e.fc40
Architektur : x86_64

Firefox from getfirefox.net will be fixed in version 130.0.
Fedora provided Firefox contains backported patches and should be fixed.
Thunderbird is not fixed yet.

Comment 30

[Ludovic Hirlimann [:Usul]]

I crash every time I close the lid of my laptop with this signature. Up to date fedora 40 using wayland.

Comment 31

[BugBot [:suhaib / :marco]]

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.

Comment 32

[Magnus Melin [:mkmelin]]

MOZ_CRASH Reason: (gnome) unknown object (98), message leave(uo) Proxy: WP:E WP:CA WP:CPCA

Comment 33

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

If you can reproduce please run on terminal with WAYLAND_DEBUG=1 MOZ_LOG"WidgetWayland:5" env variables and attach the log here.
Thanks.

Comment 34

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

Bug 1941119 is for D&D variant of this bug.

Comment 35

[Magnus Melin [:mkmelin]]

(I was just looking at the crash reports, haven't had it myself.)

Comment 36

[GreyXor]

https://crash-stats.mozilla.org/report/index/9d5a22ec-bf58-462b-960f-08c690250224#tab-details

logs:

[Parent 51812: Main Thread]: V/WidgetWayland [7f72cfd8df00]: WaylandSurface::RequestFrameCallbackLocked(), enabled 1 mapped 1 emulate 0 mFrameCallback 0
[Parent 51812: Main Thread]: V/WidgetWayland [7f72cfd8df00]: WaylandSurface::Commit() needs commit 1, force commit 0 flush 0
[Parent 51812: Main Thread]: V/WidgetWayland [7f72c4c83c00]: WaylandSurface::GetScale() fractional scale 2.000000
[Parent 51812: Main Thread]: V/WidgetWayland [7f72bd17a580]: WaylandSurface::GetScale() parent scale 2.000000
[Parent 51812: Main Thread]: D/WidgetWayland moz_container_wayland_invalidate [7f72c6b46900]
[Parent 51812: Main Thread]: V/WidgetWayland [7f72c4c83c00]: WaylandSurface::GetScale() fractional scale 2.000000
[Parent 51812: Main Thread]: V/WidgetWayland [7f72bd17a580]: WaylandSurface::GetScale() parent scale 2.000000
[Parent 51812: Main Thread]: V/WidgetWayland [7f72cfd8df00]: WaylandSurface::Commit() needs commit 0, force commit 1 flush 0
[Parent 51812: Main Thread]: D/WidgetWayland [7f72bd17a580]: WaylandSurface::AfterPaintHandler()
[Parent 51812: Main Thread]: V/WidgetWayland [7f72bd17a580]: WaylandSurface::Commit() needs commit 0, force commit 1 flush 0
[Parent 51812: Main Thread]: V/WidgetWayland [7f72c4c83c00]: WaylandSurface::GetScale() fractional scale 2.000000
[Parent 51812: Main Thread]: V/WidgetWayland [7f72bd17a580]: WaylandSurface::GetScale() parent scale 2.000000
[Parent 51812: Main Thread]: V/WidgetWayland [7f72c4c83c00]: WaylandSurface::GetScale() fractional scale 2.000000
[Parent 51812: Main Thread]: V/WidgetWayland [7f72bd17a580]: WaylandSurface::GetScale() parent scale 2.000000
[Parent 51812: Renderer]: V/WidgetWayland [7f72c4c83c00]: WaylandSurface::GetScale() fractional scale 2.000000
[Parent 51812: Renderer]: V/WidgetWayland [7f72bd17a580]: WaylandSurface::GetScale() parent scale 2.000000
[Parent 51812: Renderer]: V/WidgetWayland [7f72bd17a580]: WaylandSurface::Commit() needs commit 0, force commit 1 flush 0
[GFX1-]: () Wayland protocol error: wl_surface#869: error 2: Buffer size (1x1) is not divisible by scale (2)

ExceptionHandler::GenerateDump attempting to generate:/home/greyxor/.mozilla/firefox/9gu6g1ie.default-nightly/minidumps/32ce706f-dd43-c2e5-d44d-50272dcddf1d.dmp

Comment 37

[GreyXor]

happened with gfx.webrender.compositor.force-enabled

Comment 38

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Hello! I can reproduce this crash constantly (crash report) with Firefox 140.0a1 (2025-05-19) by following the next steps on Ubuntu 24.04:

1. Download mozregerssion and open it
2. Click on Help > About.
3. Set a Firefox .tar.xz build as default and close it.
4. Click on the github link from the mozregerssion about window.
5. Scroll the Firefox page using mouse wheel.
   AR: Firefox crashes. If more information is needed please let me know.

Comment 39

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

(In reply to Alexandru Trif, Desktop Test Engineering [:atrif] from comment #38)

Hello! I can reproduce this crash constantly (crash report) with Firefox 140.0a1 (2025-05-19) by following the next steps on Ubuntu 24.04:

1. Download mozregerssion and open it
2. Click on Help > About.
3. Set a Firefox .tar.xz build as default and close it.
4. Click on the github link from the mozregerssion about window.
5. Scroll the Firefox page using mouse wheel.
   AR: Firefox crashes. If more information is needed please let me know.

Please run on terminal with WAYLAND_DEBUG=1 env variable and attach the log here.
Thanks.

Comment 40

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Attachment: log.txt

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

Please run on terminal with WAYLAND_DEBUG=1 env variable and attach the log here.
Thanks.

Hello! Sure thing. I needed to use a script to set the variable since I needed to open Firefox through mozregression. I hope that this is the correct log; if not, please let me know. Thanks!

Comment 41

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

(In reply to Alexandru Trif, Desktop Test Engineering [:atrif] from comment #40)

Created attachment 9488843 [details]
log.txt

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

Please run on terminal with WAYLAND_DEBUG=1 env variable and attach the log here.
Thanks.

Hello! Sure thing. I needed to use a script to set the variable since I needed to open Firefox through mozregression. I hope that this is the correct log; if not, please let me know. Thanks!

Please attach about:support from version which crashes for you.
Also please run the broken version on terminal as:

WAYLAND_DEBUG=1 ./firefox > run.txt 2>&1

and attach the run.txt file here.
Thanks.

Comment 42

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Attachment: log and support.zip

I hope this is ok, if not, please let me know. Thank you!

Comment 43

[Wren Falcon]

Attachment: v140.0.4 run and support.zip

Crash using drag-and-drop on Firefox 140.0.4, Ubuntu 25.04. Crash report: https://crash-stats.mozilla.org/report/index/a444acff-4db9-4767-8b0c-c0a790250723

Seems inconsistent. Let me know if anything else is needed.

Comment 44

[Alban Browaeys]

Attachment: about:support of the Firefox that crashes dropping a file from another virtual desktop

Firefox 138.0.1 64 bits on Debian Trixie amd64
https://crash-stats.mozilla.org/report/index/4a84551d-5899-420f-a3eb-d842c0250912#tab-bugzilla
https://crash-stats.mozilla.org/report/index/92c89b09-d4c7-4f13-97c7-e44600250912#tab-bugzilla
https://crash-stats.mozilla.org/report/index/8898740d-f970-4f70-b45a-af7890250912
could this be related?

Note that I can reproduce dragging and dropping a file from nautilus 48.3 to a Github issue text area, but only if dragging from a nautilus window on another virtual desktop than the Firefox window. If both are on the same virtual desktop, no Firefox crash. Gnome Shell wayland 48.4.

I will try a run with 



about:support

Comment 45

[Alban Browaeys]

Attachment: run.txt.zip WAYLAND_DEBUG=1 run of firefox crashing dropping a non empty file from another virtual desktop

WAYLAND_DEBUG=1 /usr/bin/firefox > run.txt 2>&1 output while Firefox crashes, dropping a file from a nautilus window on another virtual desktop

Comment 46

[Alban Browaeys]

same crash dropping from nautilus 48.3 on another gnome shell 48.4 wayland virtual desktop with WAYLAND_DEBUG=1 /usr/bin/firefox > run.txt 2>&1
https://bugzilla.mozilla.org/attachment.cgi?id=9513058
https://crash-stats.mozilla.org/report/index/496e221c-100d-4e51-8c15-6a0e20250912

Comment 47

[Alban Browaeys]

Note that if the dropped file is empty, Firefox does not crash when dropping a file from a nautilus window running on another virtual workspace

Comment 49

[BugBot [:suhaib / :marco]]

Copying crash signatures from duplicate bugs.

Comment 50

[Thinker Li [:sinker]]

This bug represents crashes in mozilla::widget::WlLogHandler, which is Firefox's Wayland protocol error handler. This is a symptom/sink bug, not a root cause bug.

How WlLogHandler works:

When ANY Wayland protocol error occurs, the Wayland client library calls our log handler (WlLogHandler), which then calls MOZ_CRASH with the specific error message. This means:

1. All Wayland protocol errors crash here (with one exception)
2. The crash signature is the same (mozilla::widget::WlLogHandler)
3. But the root causes are completely different

Please do NOT mark bugs as duplicates based on signature alone!

Instead, check the MOZ_CRASH Reason field to identify the actual Wayland protocol error:

• Buffer scaling errors: "Buffer size (1x1) is not divisible by scale (2)" → Separate bug
• dmabuf import failures: "failed to import supplied dmabufs" → Bug 1989726
• Connection loss: "Error reading events from display" → Bug 1984696
• Invalid timestamps: Different issue entirely
• etc.

Each distinct Wayland protocol error deserves its own bug so we can:

1. Track specific root causes
2. Implement targeted fixes
3. Measure fix effectiveness

What should be duplicates:

Only bugs with the same MOZ_CRASH Reason (same underlying Wayland protocol error) should be marked as duplicates of each other. Consider using "See Also" to link related Wayland crashes instead.

Planned fix:

I'm working on a patch to modify WlLogHandler to call separate crash functions based on error message patterns. This will create distinct crash signatures for different Wayland protocol errors, making it much easier to track and fix specific issues automatically.

Comment 51

[Jens Stutte [:jstutte]]

It looks like we have the following cases now:

2 	mozilla::widget::WlLogHandler_ColorManagerInvalidOutput   Add term 	3 	20.00 % 	
3 	mozilla::widget::WlLogHandler_MessageLengthExceeded   Add term 	2 	13.33 % 	
4 	mozilla::widget::WlLogHandler_UnknownObject   Add term 	2 	13.33 % 	NEW 1996736
5 	mozilla::widget::WlLogHandler_InvalidSurfaceFrame   Add term 	1 	6.67 % 	
6 	mozilla::widget::WlLogHandler_MarshallingError   Add term 	1 	6.67 % 	
7 	mozilla::widget::WlLogHandler_ViewportBufferBounds   Add term 	1 	6.67 % 	

I assume we should just file separate bugs for each (and reduce severity here)?

Comment 52

[Thinker Li [:sinker]]

Sicne the patch to separate signatures is working, we will see new bugs being created. So, I downgrade to s3. We may still need some crash signatures that are not captured by the patch. I will keep eyes on them, and separate them again if necessary.

Comment 54

[Thinker Li [:sinker]]

The current distribution:

1 	mozilla::widget::WlLogHandler_ViewportBufferBounds   Add term 	11 	39.29 % 	
2 	mozilla::widget::WlLogHandler   Add term 	9 	32.14 % 	1932639 1917558 1909172 1908825 1863047 1850124 1844653 1832760
3 	mozilla::widget::WlLogHandler_InvalidDisplayObject   Add term 	3 	10.71 % 	
4 	mozilla::widget::WlLogHandler_RegistryError   Add term 	2 	7.14 % 	
5 	mozilla::widget::WlLogHandler_UnknownObject   Add term 	2 	7.14 % 	1996736
6 	mozilla::widget::WlLogHandler_MarshallingError   Add term 	1 	3.57 % 	

WlLogHandler() is still at the second place. However, WlLogHandler_ViewportBufferBounds just popped up.

Comment 55

[Sylvestre Ledru [:Sylvestre]]

Attachment: Bug 1863047 - Give Wayland compositor connection-loss errors a distinct crash signature r=stransky

The MOZ_CRASH reason "Error reading events from display: Broken pipe"
means the Wayland compositor terminated our connection (session end,
monitor hot-unplug, KVM switch), which is outside Firefox's control.
It currently falls through to the generic WlLogHandler fallback and gets
lumped into the catch-all crash signature.

Dispatch it to a dedicated MOZ_NEVER_INLINE crash function so it gets its
own signature, matching the ongoing effort to split distinct Wayland
protocol errors apart. See Bug 1984696 for the underlying issue.

Crash reports:
https://crash-stats.mozilla.org/search/?moz_crash_reason=~Error%20reading%20events%20from%20display%3A&_facets=signature&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports

Comment 56

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/3b5d30d67e29
https://hg.mozilla.org/integration/autoland/rev/f37017a2b5d2
Give Wayland compositor connection-loss errors a distinct crash signature r=stransky

Comment 57

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/f37017a2b5d2

Comment 58

[Sylvestre Ledru [:Sylvestre]]

not sure it fixes the crash but it will help with triage

Comment 59

[BugBot [:suhaib / :marco]]

The patch landed in nightly and beta is affected.
:Sylvestre, is this bug important enough to require an uplift?

• If yes, please nominate the patch for beta approval.
  • See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
• If no, please set status-firefox153 to wontfix.

For more information, please visit BugBot documentation.

Comment 60

[Sylvestre Ledru [:Sylvestre]]

let it ride the train