Bug 1889251

I have the same version of firefox/fedora.  I don't see any crashes reported by coredumpctl, but my firefox "crashes" several times a day - I don't see a core, but firefox exits, and I see messages like this in the journal:

Oct 19 14:09:56 localhost.localdomain firefox.desktop[167195]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

You won't see the crash in coredumpctl unless you run with MOZ_CRASHREPORTER_DISABLE=1 set in the environment as firefox has it's own builtin crash reporter that kicks in instead.

I didn't see a core dump, but I did see this message:

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

Gdk-Message: 19:54:18.997: Error flushing display: Broken pipe
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=8183.13) Exiting due to channel error.
Exiting due to channel error.

so I'm not sure if this is https://bugzilla.redhat.com/show_bug.cgi?id=1888920

In my case I don't have multiple workspaces, but it seems to be related to switching windows e.g. using Alt-Tab or using the hotspot with the mouse.

It's still crashing - I just updated to firefox 82.0-4 on f32

This is getting to be a problem - crashing several times a day - I'm considering switching to chrome (and as a former Netscape employee, that kills me to write)

I also saw my crashes persist after updating to Firefox 82 but the good news is that yesterday I updated to Fedora 33 and 30 hours later I haven't had a single crash yet.

It might be that a reboot, or at least a desktop restart, would have the same effect in Fedora 32 if it's related to the wider desktop stack. I agree that things like switching desktop appeared to be a trigger for me, as did things like trying to save a download, but sometime they just seemed to be spontaneous.

(In reply to Rich Megginson from comment #4)
> In my case I don't have multiple workspaces, but it seems to be related to
> switching windows e.g. using Alt-Tab or using the hotspot with the mouse.
> 
> It's still crashing - I just updated to firefox 82.0-4 on f32
> 
> This is getting to be a problem - crashing several times a day - I'm
> considering switching to chrome (and as a former Netscape employee, that
> kills me to write)

See https://fedoramagazine.org/firefox-tips-for-fedora-31/
You can switch back to X11 backend for Firefox if Wayland is too raw for you.

It seems to happen in WaylandAllocateShmMemory() when the Shm allocation fails. Let's make it more flexible in such case and don't crash.

I guessed it might be a shm allocation failure given the backtrace, but as far as I could see I was nowhere near any limits on shm availability. I have 32Gb of RAM and a 16Gb limit on shm and firefox was only using a few hundred megabytes.

(In reply to Tom Hughes from comment #8)
> I guessed it might be a shm allocation failure given the backtrace, but as
> far as I could see I was nowhere near any limits on shm availability. I have
> 32Gb of RAM and a 16Gb limit on shm and firefox was only using a few hundred
> megabytes.

Good to know. OTOH Firefox may have a sandbox restriction on Shm usage.

Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1673313

As it happens this morning I had a crash (some 72 hours after rebooting) with Fedora 33/Firefox 82. I didn't have the crash reporter disabled so I can't say for sure it's the same crash.

The fix is backported to firefox-82.0-8 builds.

FEDORA-2020-bcfc7810a7 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-bcfc7810a7

FEDORA-2020-9365bd146c has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9365bd146c

FEDORA-2020-9365bd146c has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-9365bd146c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9365bd146c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-bcfc7810a7 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-bcfc7810a7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-bcfc7810a7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Thanks, that is good news, though I haven't seen any crashes since tweaking my earlyoom settings.

FEDORA-2020-4a0e4504c6 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2020-871455fdcf has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-871455fdcf`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-871455fdcf

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-871455fdcf has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.