1728322 - Wayland Crash KDE: Error 22 (Invalid argument) dispatching to Wayland display.

Status: UNCONFIRMED

(Core :: Widget: Gtk, defect)

Description

[Henning_w_public_mail]

Attachment: firefox_crash_shortened.log

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

Steps to reproduce:

Right click on a link -> "Open Link in New Private Window"

This is not reproducible reliably.

Actual results:

Firefox crashes, stderr output of the last 5 seconds with WAYLAND_DEBUG=1 is attached.

This happens on normal browsing once every few hours. The os is OpenSuse Tumbleweed. The monitor setup consists of a 1080p laptop display scaled to 135% and a 1200p monitor scaled 100%.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Darkspirit]

Thanks for the report! Please open about:support, click on "Copy text to clipboard" and paste it here.

Comment 3

[Henning_w_public_mail]

Attachment: about:suport output

###!!! [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][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

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.
Exiting due to channel error.
Killed

Comment 4

[Henning_w_public_mail]

Attachment: Output of: rg '^###!!! ' firefox_stderr.log -B 120 -A 60 > firefoxChannel_closing_too_late.log

Sorry after attaching the log as a file, it automatically send a reply and I can't edit this any more.

I have noticed another strange thing that might be related, it got the following messages and when hovering over the Firefox icon in the task bar for a preview Firefox crashed. I don't know if these messages came in successtion or not but I found them in my old log too. I'll attach a snippet of the old log. These are the messages:

###!!! [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][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

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.
Exiting due to channel error.
Killed

Comment 5

[Darkspirit]

Can it be fixed by disabling gfx.webrender.compositor and gfx.webrender.compositor.force-enabled and restarting Firefox?

Comment 6

[renyuneyun]

I'm having the same issue. The error is the same, except for the number: [e-mail]

I checked that gfx.webrender.compositor and gfx.webrender.compositor.force-enabled are both disabled (by default).

Comment 7

[renyuneyun]

I also found this bug somewhere else: https://github.com/swaywm/wlroots/issues/2594.
Maybe this is not simply a firefox issue?

Comment 8

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

Do you still see that on KDE?
thanks.

Comment 9

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

(In reply to renyuneyun from comment #7)

I also found this bug somewhere else: https://github.com/swaywm/wlroots/issues/2594.
Maybe this is not simply a firefox issue?

If it can be reproduced on more Wayland compositors (KDE, Sway) it may be a Firefox issue.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:stransky, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?

For more information, please visit auto_nag documentation.