Open Bug 1538435 Opened 11 months ago Updated 2 months ago

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

Categories

(Core :: Graphics, defect, P3)

68 Branch
defect

Tracking

()

UNCONFIRMED
Tracking Status
firefox68 --- affected
firefox69 --- affected
firefox70 --- affected
firefox71 --- affected

People

(Reporter: mikhail.v.gavrilov, Unassigned)

References

Details

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.

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