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

Steps to reproduce:

1. Open firefox 86.0b7 in wayland
2. Switch tabs, navigate, etc.
3. Focus another non-firefox window on your desktop
4. Go back to firefox

Actual results:

Firefox UI freezes after switching to firefox window

Expected results:

Firefox UI should not freeze

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.

Perhaps I should have specified that I'm using sway 1.5 which uses wlroots.

Still happening on 87.0b8

Probably related to #1691738

When I use MOZ_WEBRENDER=0 the problem goes away.

https://bugzilla.mozilla.org/show_bug.cgi?id=1691738

The problem persists even if MOZ_WEBRENDER=0 is used.

Today, during a google meets call it froze again, these are the logs.

(firefox:1226534): Gdk-CRITICAL **: 11:17:56.956: gdk_wayland_window_remove_frame_callback_surface: assertion 'surface != NULL' failed
IPDL protocol error: Handler returned error code!

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

[Parent 1226534, IPC I/O Parent] WARNING: Message needs unreceived descriptors channel:7f3242515480 message-type:65531 header()->num_fds:1 num_fds:0 fds_i:0: file /builds/worker/checkouts/gecko/ipc/chromium/src/chrome/common/ipc_channel_posix.cc:483
Sandbox: bad read from pid 1227849: Message too long
Sandbox: Unexpected EOF, op 0 flags 02000000 path /sys/devices/system/cpu/online
Sandbox: bad read from pid 1227890: Message too long
Sandbox: Unexpected EOF, op 0 flags 00 path /proc/1227890/statm
Sandbox: bad read from pid 1226669: Message too long
Sandbox: Unexpected EOF, op 0 flags 00 path /proc/1226669/statm
Sandbox: bad read from pid 1226714: Message too long
Sandbox: Unexpected EOF, op 0 flags 00 path /proc/1226714/statm
Sandbox: bad read from pid 1226761: Message too long
Sandbox: Unexpected EOF, op 0 flags 00 path /proc/1226761/statm
Sandbox: bad read from pid 1227577: Message too long
Sandbox: Unexpected EOF, op 0 flags 00 path /proc/1227577/statm
Sandbox: bad read from pid 1226620: Message too long
Sandbox: Unexpected EOF, op 0 flags 00 path /proc/1226620/statm
Sandbox: bad read from pid 1227748: Message too long
Sandbox: Unexpected EOF, op 0 flags 00 path /proc/1227748/statm

Today it crashed and produced this log

###!!! [Parent][DispatchAsyncMessage] Error: PCompositorBridge::Msg_PAPZCTreeManagerConstructor Value error: message was deserialized, but contained an illegal value

###!!! [Parent][DispatchAsyncMessage] Error: PCompositorBridge::Msg_PAPZConstructor Value error: message was deserialized, but contained an illegal value

(In reply to javiertury from comment #6)

Today, during a google meets call it froze again, these are the logs.

(firefox:1226534): Gdk-CRITICAL **: 11:17:56.956: gdk_wayland_window_remove_frame_callback_surface: assertion 'surface != NULL' failed

This error line was introduced in bug 1668805, however it's likely that the actual error happened earlier and only triggered the assert here. It would be great to know if things get better with sway 1.6 once it's out.

(In reply to Robert Mader [:rmader] (back on ~23. Nov) from comment #8)

... It would be great to know if things get better with sway 1.6 once it's out.

javiertury,

Is it Better now?

Yes, this problem is gone in version 1.6-1