Open Bug 1538435 Opened 3 years ago Updated 10 days ago

[Wayland] Firefox can self closed randomly (Exiting due to channel error)

Categories

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

68 Branch
defect

Tracking

()

UNCONFIRMED
Tracking Status
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- wontfix
firefox71 --- wontfix
firefox74 --- wontfix
firefox75 --- wontfix
firefox76 --- fix-optional

People

(Reporter: mikhail.v.gavrilov, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

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

Steps to reproduce:

I use latest nightly build:

$ Downloads/firefox/firefox
*** You are running in chaos test mode. See ChaosMode.h. ***
IPDL protocol Error: Received an invalid file descriptor
IPDL protocol Error: Received an invalid file descriptor

###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

IPDL protocol Error: Received an invalid file descriptor
IPDL protocol Error: Received an invalid file descriptor
IPDL protocol Error: Received an invalid file descriptor
[Child 12869, Chrome_ChildThread] WARNING: pipe error (56): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
[Child 12854, Chrome_ChildThread] WARNING: pipe error (57): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
[Child 12854, Chrome_ChildThread] WARNING: pipe error (55): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=1.89439) [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[Child 12869, Chrome_ChildThread] WARNING: pipe error (53): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=2.25399) [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[Child 12869, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
Exiting due to channel error.
[Child 12854, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=5.19836) Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=7.18981) [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[Child 12752, Chrome_ChildThread] WARNING: pipe error (52): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
[Child 12752, Chrome_ChildThread] WARNING: pipe error: Broken pipe: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 726
Exiting due to channel error.
[Child 12800, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=11.0966) [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[Child 12661, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
Exiting due to channel error.

Actual results:

Firefox crashed (self closed)

Component: Untriaged → Graphics
Product: Firefox → Core
Priority: -- → P3

How can I provide the needed info ?

I'm running firefox which is crashing all the time (6 ~ 12 minutes after launching it) I try to use it since 2 years ago. The crashes reported on about:crashes are not any more at your bugtracker due 6 month limit policy

Currently at firefox 69 on Debian Sid, i tried to download firefox from upstream too. Both, normal mode and safe-mode crash. Disabling hardware acceleration not help. Creating a new ~/.mozilla not help.

$ firefox
[Child 20457, Chrome_ChildThread] WARNING: pipe error (3): Conexión reinicializada por la máquina remota: file /build/firefox-W4ZBKx/firefox-69.0.1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.
Terminado (killed)

I was a happy firefox user until it started to crash on my computer. Please see that other apps will not crash

Please help me fixing my firefox issue

Thank you!

I'm affected as well. Version 68 worked correctly.

Now, the Firefox 69.0.1 is always crashing when I try open the hamburger menu or type any text (url, text to search) into address bar. FF fails with the same error as i5513 have.

As long I don't open menu or enter text into address bar, FF works.

I'm on Gentoo, KDE plasma 5.16.5., kernel 5.3.1-gentoo, old nvidia graphics (GeForce GT 740M) with 435.21 drivers used together with build-in Intel GC.

Update: returned to FF 68 and all works, no crashes.

So I have other two computers where FF 69 works.

On this one, where it fails, I had some issues with overheating. I have solved and recompiled gcc and FF 69 and it works correctly now. So it was probably issue with corrupted gcc.

Today I tried a firefox snap version, but it didn't work :(. Firefox wont run more than 5- 10 minutes at my laptop.
$ snap list firefox
Name Version Rev Tracking Publisher Notes
firefox 69.0.3-1 274 stable mozilla✓ -

[Child 15392, MediaDecoderStateMachine #1] WARNING: Decoder=7f4ed2df2800 Decode error: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006) - static MP4Metadata::ResultAndByteBuffer mozilla::MP4Metadata::Metadata(mozilla::ByteStream *): Cannot parse metadata: file /builds/worker/workspace/build/src/dom/media/MediaDecoderStateMachine.cpp, line 3309
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
user-open error: no such file or directory
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
user-open error: no such file or directory
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Terminado (killed)

Tried beta version at snap , the same result:

$ snap list firefox
Name Version Rev Tracking Publisher Notes
firefox 70.0b14-1 275 beta mozilla✓ -

LibThai: Fail to open dictionary at '/usr/share/libthai/thbrk.tri'.
LibThai: Fail to open dictionary at '/usr/share/libthai/thbrk.tri'.
LibThai: Fail to open dictionary at '/usr/share/libthai/thbrk.tri'.
[Parent 19755, Gecko_IOThread] WARNING: pipe error (143): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 19755, Gecko_IOThread] WARNING: pipe error (256): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Child 20304, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Terminado (killed)

How can we debug this issue? I would like to stick to firefox ... but for now I have to use chrome (since 2 years :( )

Thank you !

tried with Xorg classic and with wayland, the same result

Seeing this with Firefox 71.0 on Arch Linux.

Dec 07 16:17:27 miner firefox.desktop[3372]: [Parent 3372, Gecko_IOThread] WARNING: pipe error (260): Connection reset by peer: file /build/firefox/src/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Dec 07 16:17:27 miner firefox.desktop[3372]: [Parent 3372, Gecko_IOThread] WARNING: pipe error (192): Connection reset by peer: file /build/firefox/src/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Dec 07 16:17:27 miner firefox.desktop[3372]: [Parent 3372, Gecko_IOThread] WARNING: pipe error (227): Connection reset by peer: file /build/firefox/src/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Dec 07 16:17:27 miner firefox.desktop[3372]: [Parent 3372, Gecko_IOThread] WARNING: pipe error (190): Connection reset by peer: file /build/firefox/src/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Dec 07 16:17:28 miner firefox.desktop[3428]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
Dec 07 16:17:28 miner firefox.desktop[3372]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
Dec 07 16:17:28 miner firefox.desktop[3372]: [Parent 3372, Gecko_IOThread] WARNING: pipe error (82): Connection reset by peer: file /build/firefox/src/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Dec 07 16:17:28 miner firefox.desktop[3372]: ###!!! [Child][MessageChannel::SendAndWait] Error: Channel error: cannot send/recv

I have this issue:

  • Firefox 71.0 (64-bit)
  • NixOS
  • Sway

This has only happened to be on reddit.com (new), although it could be pure coincidence. Each time I restart my browser and visit the same reddit pages, it crashes after some time.

(firefox:5267): Gdk-WARNING **: 16:12:05.261: (../gdk/wayland/gdkwindow-wayland.c:810):buffer_release_callback: runtime check failed: (impl->staging_cairo_surface != cairo_surface)
JavaScript error: , line 0: uncaught exception: Object
JavaScript error: , line 0: uncaught exception: undefined
JavaScript error: , line 0: uncaught exception: undefined
JavaScript error: , line 0: uncaught exception: undefined
JavaScript error: , line 0: uncaught exception: undefined
.firefox-wrapped: cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&surface->ref_count)' failed.
[Child 5689, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Child 5502, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Exiting due to channel error.
[Child 5493, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Exiting due to channel error.
[Child 5530, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Child 5449, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
[Child 5422, Chrome_ChildThread] WARNING: pipe error (55): Connection reset by peer: file /build/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=69.7012) [Child 5393, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=69.7892) Exiting due to channel error.
[Child 5422, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Exiting due to channel error.
[Child 5321, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Exiting due to channel error.
Aborted (core dumped)

Firefox crashing also seems to be linked with opening links by calling the firefox executable.

If I have Firefox already opened and type:

$ firefox 'youtube.com'

Then when I am going to interact with the new tab that was created by that command, the browser will crash. It seems to be the best way I can find to reproduce it. I have also tried with other websites (change youtube.com in the above example), and have the same problem.

Could anyone confirm that this is the problem? And that it is reproducible?

(In reply to nils from comment #10)

Firefox crashing also seems to be linked with opening links by calling the firefox executable.

If I have Firefox already opened and type:

$ firefox 'youtube.com'

Then when I am going to interact with the new tab that was created by that command, the browser will crash. It seems to be the best way I can find to reproduce it. I have also tried with other websites (change youtube.com in the above example), and have the same problem.

Could anyone confirm that this is the problem? And that it is reproducible?

I can always reproduce it.

This started happening constantly for me starting with today's nightly update using the wayland backend.
GDK_BACKEND=wayland /.../firefox-nightly/firefox

Gdk-Message: 13:04:57.986: Error flushing display: Invalid argument
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.

Firefox Version: 73.0a1 (2020-01-03) (64-bit)

Note that the above steps mentioned by :nils does not consistently reproduce the issue I'm seeing.

I also want to mention that I just switched to an SSD and my computer has a lot less latency now. For example firefox takes a lot less time to startup.

I'm still running firefox 71 and am running the same OS (NixOS) but now it just isn't reproduceable.

This could suggest this crash is caused by a race condition or something of that kind.

I get the issue on an SSD. The one pattern I've noticed is that it tends to crash shortly after waking and logging in (after automatic suspend). Does anyone else get the Firefox window going transparent when it crashes. It's as if the window becomes hollow with only a frame. I can see through to my desktop. Firefox doesn't actual close until I hit the close icon. But I get the same "Error: Channel closing: too late to send/recv, messages will be lost" message.

I started seeing this after yesterday's nightly update as well. I'm on Wayland (swaywm).

$ GDK_BACKEND=wayland ./firefox
Gdk-Message: 15:57:53.832: Error 22 (Invalid argument) dispatching to Wayland display.
Exiting due to channel error.

This is very frequent for me—it's probably already happened like four times today.

I can't find a consistent way to reproduce the crash in comment 12, but it seems to happen at random and fairly often.

Workaround: I only see it when running with GDK_BACKEND=wayland. If I simply run firefox-nightly/firefox & (as I'm doing right now), the issue disappears.

Here's some environment info:

Firefox Version: *73.0a1* (2020-01-04) (64-bit)
Arch Linux
Gnome Version 3.34.2 (Wayland)
graphics card:
                       nVidia GP107M [GeForce GTX 1050 Ti Mobile]
                       Intel UHD Graphics 630 (Mobile)
cpu:
                       Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz, 3955 MHz (6 core, 6 virtual)
disk:               SK hynix SSD

Problem on wayland might be dup of Bug 1606751 .

See Also: → 1606751

Just to note, I'm no longer seeing this issue on the latest nightly build with Wayland. So most likely my problem (which could be different from this bug) was indeed fixed in Bug 1606751.

I also see Firefox randomly exits.

i@alexei:~$ firefox --private-window; echo $?
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
CPU time limit exceeded (core dumped)
152

It seems to correlate with opened tab of purrli.com -- when the site is opened, I have an exit in about 0.5--2 hours, and otherwise it at least works much longer.
No new items appear in about:crashes, no files in /var/crash/, despite phrase "core dumped" in output and ulimit -c unlimited.

Ubuntu 18.04, Firefox 74 (and earlier versions too). Addons used: Adblock Plus (without it I can't reproduce, with it Firefox exits after several hours of running one tab with purrli.com).

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Keywords: regression
Keywords: regression

For me Firefox-68.6.0esr-x86_64 ALWAYS crashes immediately after starting it with messages:

Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=1.89439) [GFX1-]: Receive IPC close with reason=AbnormalShutdown

I've tried to reinstall system and at the moment I'm using Slackware64-current PLASMA5 live USB.
The notebook on which the crashes always reproduce is:
Manufacturer: Acer
CPU: AMD C-50
GPU: AMD 6250 (integrated with CPU)

I haven't had any success with the recent Firefox versions on this netbook - that is, when
(and if) a version of Firefox (in fact I think those were only Slackware-provided ESRs) runs
without the mentioned crash it anyway is inevitable unuseful because of permanent
"GAH your tab has crashed"'s on every tab but text-only (or maybe absolute static).

The strange (or maybe good) thing is that I've boot from the same USB stick another
notebook(s) (with an older Intel CPU / integrated GPU) - and have had NO problems at all.
So I think that there maybe some hardware/GPU drivers incompatibility involved in these
crashes....

Any progress? I'm experiencing these crashes on firefox-78.0.1 under Wayland (Sway 1.5)

Seems to be fixed at Debian Unstable, Firefox 79

Yesterday firefox run fine about three hours, now I'm browsing 36 minutes without any crash

I hope other affected people can confirm it !

I have the problem since I have upgraded firefox to version 80.
I have followed minor update from Gentoo and now I'm using 80.0.1
When firefox crash, I can get this message in the terminal :

Crash Annotation
GraphicsCriticalError: |
[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=31.4298)
Crash Annotation
GraphicsCriticalError: |
[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=31.2482)
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Crash Annotation
GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=32.4313)
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Crash Annotation
GraphicsCriticalError: |
[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=31.5242)
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Erreur de segmentation (translation: segmentation fault )

In he computer that crash, there is 2 GPU :
04:00.0 VGA compatible controller: NVIDIA Corporation G96C [GeForce 9500 GT] (rev a1)
09:0c.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02)
that are used with "radeon" and "nouveau" driver.

I can reproduce the bug each time I try to visit this french bank's site

It can be easy to me to build another version of firefox with debug info to get stack, does it needed ?

I was able to get a stable build by disabling link time optimization, (-lto useflag for gentoo user)

Still happens, and only on Wayland.

Happens to me as well on a Gentoo system on Firefox 84 and 85 under certain conditions (e.g., several windows open, try to open more windows). On Wayland, the actual error is:
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=5115.14) Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=3547.66)

I haven't had a chance to try "safe" mode yet, but I'm only running Vimius-C, NoScript and AgentSwitcher, not something I would describe as "heavy extension usage".

I also started wondering why WebGL has some ANDROID in it, but that may just be spurious.

I can confirm that this happens in safe mode, too.

Please run with WAYLAND_DEBUG=1 env variable set. It should reveal if it's a problem in Wayland.
Thanks.

Blocks: wayland
Component: Graphics → Widget: Gtk
Summary: Firefox can self closed randomly (Exiting due to channel error) → [Wayland] Firefox can self closed randomly (Exiting due to channel error)

Martin, happy to test the WAYLAND_DEBUG route, which I'm familiar with and is fully independent from the program, so long as it's a wayland client, that is.
However, are you sure that coredumpctl works in this case? The page you linked says "Application window simply disappear and bug report dialog will show up" and suggests that coredumpctl is one of the things that you can do. However, this is not my case (and I thought not the case for this bug either, but I may be wrong). Firefox simply crashes and there is nothing offered, no crash saved in ~/.mozilla. Let me know if I misunderstood before I start installing more debugging tools.

If you see Mozilla crashreporter dialog please use it, submit crash (from about:crashes) and paste crash ID here. Use coredumpctl only when Mozilla crashreporter dialog does not show up. Also please inspect crashes at about:crashes if they're related.

OK - I can confirm that there is nothing in about:crashes, nor in ~/mozilla (wherever the crashes get stored) - basically Firefox has never crashed with the crashreporter in a very long time. I'll get coredumpctl and give it a try - will report if I find something relevant.

It's also possible that Firefox does not crash - it's just terminated due to Wayland protocol error. That should reveal WAYLAND_DEBUG log.

$ tail -50 firefox.log.1 
[3306822.292] wl_display@1.delete_id(312)
[3306822.335] wl_buffer@301.release()
[3306822.379] wl_buffer@172.release()
[3306822.413] wl_callback@312.done(154124)
[3306822.618] wl_buffer@290.release()
[3306833.496] wl_display@1.delete_id(88)
[3306833.591] wl_display@1.delete_id(321)
[3306833.621] wl_display@1.delete_id(320)
[3306833.647] wl_display@1.delete_id(308)
[3306833.686] wl_callback@88.done(76365597)
[3306833.759] wl_callback@320.done(76365597)
[3306833.864] wl_callback@321.done(76365597)
[3306833.946] wl_callback@308.done(76365597)
[3307167.026]  -> wl_compositor@6.create_surface(new id wl_surface@308)
[3307257.694]  -> wl_surface@30.destroy()
[3307258.855]  -> wl_surface@27.destroy()
[3307259.868]  -> zwp_linux_dmabuf_v1@29.destroy()
[3307361.558]  -> wl_surface@308.frame(new id wl_callback@321)
[3307361.709]  -> xdg_wm_base@25.get_xdg_surface(new id xdg_surface@320, wl_surface@308)
[3307361.742]  -> xdg_surface@320.get_toplevel(new id xdg_toplevel@88)
[3307361.764]  -> xdg_toplevel@88.set_parent(nil)
[3307361.787]  -> xdg_toplevel@88.set_title("Mozilla Firefox")
[3307361.808]  -> xdg_toplevel@88.set_app_id("firefox-wayland")
[3307361.827]  -> wl_surface@308.commit()
[3307361.844]  -> org_kde_kwin_server_decoration_manager@11.create(new id org_kde_kwin_server_decoration@312, wl_surface@308)
[3307361.876]  -> org_kde_kwin_server_decoration@312.request_mode(2)
[3307380.879]  -> wl_shm@45.create_pool(new id wl_shm_pool@189, fd 228, 4)
[3307381.139]  -> wl_shm_pool@189.create_buffer(new id wl_buffer@183, 0, 1, 1, 4, 0)
[3307438.980]  -> wl_buffer@183.destroy()
[3307439.040]  -> wl_shm_pool@189.destroy()
[3307439.120]  -> xdg_toplevel@88.destroy()
[3307439.138]  -> xdg_surface@320.destroy()
[3307439.150]  -> org_kde_kwin_server_decoration@312.release()
[3307439.162]  -> wl_surface@308.destroy()
[3307443.120] wl_display@1.delete_id(183)
[3307443.179] wl_display@1.delete_id(189)
[3307443.202] wl_display@1.delete_id(88)
[3307443.226] wl_display@1.delete_id(320)
[3307443.250] wl_display@1.delete_id(312)
[3307443.277] wl_display@1.delete_id(321)
[3307443.305] wl_display@1.delete_id(308)
[3307443.331] xdg_wm_base@25.ping(Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=46.1424) Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=46.6436) Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.

Not sure this is too useful... maybe the server killed firefox because it took a long time to return a pong? I'll come back with that coredumpctl if/when it crashes again and I get it installed :)

[3307443.331] xdg_wm_base@25.ping(Exiting due to channel error.

Yes, this is important. I suggest to report it to KWim/Wayland for further investigation. Maybe some KWim log can help here but I don't know how to get it, Vlad?

Flags: needinfo?(vlad.zahorodnii)
Blocks: wayland-kde
No longer blocks: wayland

Martin, FWIW, I don't use KDE/Plasma... I'm on hikari (wlroots based compositor). If you tell me what you're looking for exactly, I can poke around a bit - my understanding is that Wayland server uses ping/pong to figure out if something is deadlocked. The indication of "clients have to respond to a ping in a timely manner" doesn't really describe what ought to happen very well, and I'm not an expert here but anything I can do to help, I will do.

Gabriel: what would be interesting if still see the crashes when using nightly (as there have been a bunch of crash fixes that are not yet in release). And also if forcing on Webrender makes any difference (should be automatically enabled on nightly).

Thanks, Robert. I activated webrender and went ahead to refresh the 16 windows (assuming that that's the way to make this kick in), and crashed :) Attaching last 1000 lines of the wayland log.
Martin, sorry, I can see there is something related to kwin in the wayland logs :)

Martin: regarding coredumpctl, I am not on systemd, so can't provide that. There are, however, no core dumps or any logs beyond what I provided from stdin+stderr

Okay, Thanks for the info. I think it would help to get log from the compositor or ask compositor devs.

Flags: needinfo?(vlad.zahorodnii)

Martin, I haven't found anything in the compositor's logs - but I'll pay more attention in the next crash in case there's something not obvious. I'll share this bug in the community, see if anybody has seen the same.

Robert: it turns out that with using webrender didn't yield a crash, albeit I did see a few strange areifacts here and there, but nothing too offensive, and certainly much more pleasant than a sudden crash.
Perhaps if others want to test, it's easy to enable via about:config, and didn't even need to run nightly.
Of course luck may damn me tomorrow, in which case I will report back :)

Hit this bug again, with firefox 88 (debian unstable) :(

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

Please run with WAYLAND_DEBUG=1 env variable set. It should reveal if it's a problem in Wayland.
Thanks.

Tried it but not success

javi@doraemon:$ WAYLAND_DEBUG=1 firefox -no-safe
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Terminado (killed)
javi@doraemon:
$ sudo coredumpctl list # do I need to start some service?
No coredumps found.

in about:crash:
No crash reports have been submitted.

but at firefox directory (not *log found, but yes a crash report??)
javi@doraemon:/.mozilla/firefox/Crash Reports$ cat InstallTime20210504152106
1621797825
javi@doraemon:
/.mozilla/firefox/Crash Reports$ ls -l --full-time InstallTime20210504152106
-rw------- 1 javi disk 10 2021-05-23 21:23:45.578083218 +0200 InstallTime20210504152106

Checked with and without hardware accel checked

How can I provide logs?

Thank you!

(In reply to i5513 from comment #47)

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

Please run with WAYLAND_DEBUG=1 env variable set. It should reveal if it's a problem in Wayland.
Thanks.

Tried it but not success

javi@doraemon:$ WAYLAND_DEBUG=1 firefox -no-safe
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Terminado (killed)
javi@doraemon:
$ sudo coredumpctl list # do I need to start some service?
No coredumps found.

in about:crash:
No crash reports have been submitted.

but at firefox directory (not *log found, but yes a crash report??)
javi@doraemon:/.mozilla/firefox/Crash Reports$ cat InstallTime20210504152106
1621797825
javi@doraemon:
/.mozilla/firefox/Crash Reports$ ls -l --full-time InstallTime20210504152106
-rw------- 1 javi disk 10 2021-05-23 21:23:45.578083218 +0200 InstallTime20210504152106

Checked with and without hardware accel checked

How can I provide logs?

Thank you!

Sorry for syntax ...

javi@doraemon:~$ WAYLAND_DEBUG=1 firefox  -no-safe
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Terminado (killed)
javi@doraemon:~$ Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.

javi@doraemon:~$ sudo coredumpctl list
No coredumps found.
javi@doraemon:~/.mozilla/firefox/Crash Reports$ cat InstallTime20210504152106
1621797825javi@doraemon:~/.mozilla/firefox/Crash Reports$ ls -lrt InstallTime20210504152106
-rw------- 1 javi disk 10 may 23 21:23 InstallTime20210504152106
javi@doraemon:~/.mozilla/firefox/Crash Reports$ 

Seeing this same problem (Exiting due to channel error) every couple days on Firefox 88.0.1 (64-bit) with Wayland, Gnome 3.38.5, on Debian GNU/Linux 11 (bullseye), with NVMe SSD, no recent crash reports.

Recently Firefox has started to crash very often this way.

$ Downloads/firefox/firefox

###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
CPU time limit exceeded (core dumped)

Please open about:support, click on "Copy text to clipboard" and paste it here.

Attached file about:support

MOZ_GMP_PATH: /usr/lib64/mozilla/plugins/gmp-gmpopenh264/system-installed

media.gmp-widevinecdm.abi: x86_64-gcc3-asan

My official Nightly doesn't have an "-asan" widevine plugin, only "x86_64-gcc3".
From Firefox' official asan build I remember that it doesn't open the regular crash reporter, but has its own crash reporting: https://firefox-source-docs.mozilla.org/tools/sanitizer/asan_nightly.html Are you using this ASan Nightly, a self-compiled one, or one from which distribution?

Please try out the official Nightly from https://nightly.mozilla.org and remove the MOZ_GMP_PATH environment variable.

(In reply to Darkspirit from comment #53)

My official Nightly doesn't have an "-asan" widevine plugin, only "x86_64-gcc3".
From Firefox' official asan build I remember that it doesn't open the regular crash reporter, but has its own crash reporting: https://firefox-source-docs.mozilla.org/tools/sanitizer/asan_nightly.html Are you using this ASan Nightly, a self-compiled one, or one from which distribution?

Yes, I am use Firefox' official ASan Nightly binary downloaded from page https://firefox-source-docs.mozilla.org/tools/sanitizer/asan_nightly.html.

Please try out the official Nightly from https://nightly.mozilla.org and remove the MOZ_GMP_PATH environment variable.

It turns out that the MOZ_GMP_PATH variable was set by the script /etc/profile.d/gmpopenh264.sh, which was installed by the mozilla-openh264 package, which is installed by default in Fedora.

# cat /etc/profile.d/gmpopenh264.sh
MOZ_GMP_PATH="/usr/lib64/mozilla/plugins/gmp-gmpopenh264/system-installed"
export MOZ_GMP_PATH

[root@primary-ws /]# dnf provides /etc/profile.d/gmpopenh264.sh
Last metadata expiration check: 0:25:43 ago on Wed 01 Sep 2021 01:46:44 AM +05.
mozilla-openh264-2.1.1-2.fc35.x86_64 : H.264 codec support for Mozilla browsers
Repo        : @System
Matched from:
Filename    : /etc/profile.d/gmpopenh264.sh

mozilla-openh264-2.1.1-2.fc35.x86_64 : H.264 codec support for Mozilla browsers
Repo        : fedora-cisco-openh264
Matched from:
Filename    : /etc/profile.d/gmpopenh264.sh

[root@primary-ws /]# rpm -ql mozilla-openh264
/etc/profile.d/gmpopenh264.sh
/usr/lib/.build-id
/usr/lib/.build-id/3d
/usr/lib/.build-id/3d/fdd6769fec61f5e3a1ddc2a5c9239df8a4bcaf
/usr/lib64/firefox
/usr/lib64/firefox/defaults
/usr/lib64/firefox/defaults/pref
/usr/lib64/firefox/defaults/pref/gmpopenh264.js
/usr/lib64/mozilla/plugins/gmp-gmpopenh264
/usr/lib64/mozilla/plugins/gmp-gmpopenh264/system-installed
/usr/lib64/mozilla/plugins/gmp-gmpopenh264/system-installed/gmpopenh264.info
/usr/lib64/mozilla/plugins/gmp-gmpopenh264/system-installed/libgmpopenh264.so
/usr/lib64/mozilla/plugins/gmp-gmpopenh264/system-installed/libgmpopenh264.so.2.1.1
/usr/lib64/mozilla/plugins/gmp-gmpopenh264/system-installed/libgmpopenh264.so.6

I removed this package.

Me too, I have been experiencing this problem.

[Child 5314, MediaDecoderStateMachine #3] WARNING: Decoder=7f7f82067000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470

###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

[Child 5524, MediaDecoderStateMachine #1] WARNING: Decoder=7fa7a0bb8400 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470
[Child 5524, MediaDecoderStateMachine #1] WARNING: Decoder=7fa7a0bb8400 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470

###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

[Child 8024, MediaDecoderStateMachine #3] WARNING: Decoder=7f02360fb400 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470
[Child 8024, MediaDecoderStateMachine #3] WARNING: Decoder=7f02360f1400 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470
[Child 8024, MediaDecoderStateMachine #3] WARNING: Decoder=7f0226906400 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470
[Child 8024, MediaDecoderStateMachine #3] WARNING: Decoder=7f020bcb8c00 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470
[Child 8024, MediaDecoderStateMachine #3] WARNING: Decoder=7f021652e000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470
[Child 8024, MediaDecoderStateMachine #3] WARNING: Decoder=7f021652e000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470
[Child 5314, MediaDecoderStateMachine #23] WARNING: Decoder=7f7f8c4cf800 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp, line 3470


###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

If Firefox has run on HDD or external HDD, web page performance and speed is poor and slowest. It impacts performance of The Firefox extensions!
If Firefox runs on memory, it is speedy, but I will test then reported.

Sorry
I have tested with Firefox v78 v85 v89 on Linux and Windows! It is the same problem

You need to log in before you can comment on or make changes to this bug.