Crash randomly when opening

[flodavid]

What Happened?

Every so often, the dock crashes when I try to display it. It then restarts after a few seconds.
It only happens with the Wayland session.
It may be the same bug as #393.

Steps to Reproduce

Quickly move the mouse pointer multiple times above and "under" (even if it can still be interacted with, the mouse must be under the visible UI) the dock multiple times. If you are fast enough (if a tooltip had the time to be displayed, you are not fast enough) the dock crashes.

It is very easy to reproduce by setting the maximum mouse speed and the minimum dock height.

Expected Behavior

The dock is shown immediatly.

OS Version

8.x (Circe)

OS Architecture

amd64 (on most hardwares)

Session Type

Secure Session (Wayland, This is the default)

Software Version

Latest release (I have run all updates)

Log Output

Dock with G_MESSAGES_DEBUG=all:

(io.elementary.dock:29171): Gdk-DEBUG: 03:52:50.117: xdg_wm_base@35: error 4: wl_surface@60 already has a buffer committed

Gdk-Message: 03:52:50.117: Error 71 (Protocol error) dispatching to Wayland display.

Then the dock restarts within seconds and I have:

.02:52:52 MSI-H310Linux io.elementary.d[10981]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
02:52:52 MSI-H310Linux io.elementary.d[10981]: WorkspaceSystem.vala:98: DesktopIntegration is null
02:52:52 MSI-H310Linux io.elementary.d[10981]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

journalctl gives the following logs for gala:

02:52:50 MSI-H310Linux gala[8705]: WL: error in client communication (pid 8705)

And after restart:

02:52:52 MSI-H310Linux gala[8705]: clutter_actor_get_width: assertion 'CLUTTER_IS_ACTOR (self)' failed
02:52:52 MSI-H310Linux gala[8705]: clutter_actor_get_height: assertion 'CLUTTER_IS_ACTOR (self)' failed

I also got the following journalctl logs for gala, but I am not sure the additional logs are related :

03:05:33 MSI-H310Linux gala[8705]: meta_wayland_client_owns_window: assertion 'client->subprocess.process_running' failed
03:05:33 MSI-H310Linux gala[8705]: WL: error in client communication (pid 16029)
03:05:34 MSI-H310Linux gala[8705]: clutter_actor_get_width: assertion 'CLUTTER_IS_ACTOR (self)' failed
03:05:34 MSI-H310Linux gala[8705]: clutter_actor_get_height: assertion 'CLUTTER_IS_ACTOR (self)' failed
03:05:34 MSI-H310Linux gala[8705]: BackgroundBlurEffect.vala:344: BackgroundBlurEffect: Couldn't update framebuffers, incorrect size
03:05:34 MSI-H310Linux gala[8705]: *** BUG ***
03:05:34 MSI-H310Linux gala[8705]: In pixman_region32_init_rect: Invalid rectangle passed
03:05:34 MSI-H310Linux gala[8705]: Set a breakpoint on '_pixman_log_error' to debug
03:05:34 MSI-H310Linux gala[8705]: BackgroundBlurEffect.vala:344: BackgroundBlurEffect: Couldn't update framebuffers, incorrect size
03:05:34 MSI-H310Linux gala[8705]: *** BUG ***
03:05:34 MSI-H310Linux gala[8705]: In pixman_region32_init_rect: Invalid rectangle passed
03:05:34 MSI-H310Linux gala[8705]: Set a breakpoint on '_pixman_log_error' to debug
03:05:44 MSI-H310Linux gala[8705]: Over 50 separate vertex shaders have been generated which is very unusual, so something is probably wrong!
03:05:45 MSI-H310Linux gala[8705]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
03:06:31 MSI-H310Linux gala[8705]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

Hardware Info

Elementary OS 8.1. Linux 6.14.0-37-generic
GPU: GeForce RTX 2060 Rev. A. nvidia-driver-[570/580]-open
CPU: Hexa-Core Intel® Core(TM) i5-9400F CPU @ 2.90GHz
32 GB memory

[LuminousHustler]

This might be the same issue as #537. But you have a lot of really good information in this thread which isn't captured there. I can't reproduce either issue so I'm hesitant to say for certain if this truly is the same thing.

You noted that you're running driver v570 and v580 in the hardware section? I asked because #471 (comment) some folks were saying the issue went away in 570. (Although the root case is still unknown)

[flodavid]

I do not think it is the same issue as #537. I have the crash issue very often on Wayland but not with X. I also got the invisible dock with X (which is why I downgraded to v570), but the dock is not crashed when it happens, since we can still interact with it and the tooltips are shown. While with the crash issue, the dock briefly appears before disappearing (crashes) and it does not reappear if I juste leave the mouse "in the dock zone". I have to move the mouse at the bottom of the screen again to trigger its apparition (after it restarted, so 1~2 secs after the crash).

After using the desktop more, I discovered that the "very quickly move your mouse under the dock" is not the only way to make the dock crash, since sometimes it crashes when the dock first appears, without moving the mouse fast. But it still is a very reliable reproduction method on my system.

I can also reproduce by just hovering different application icons back and forth, instead of moving over and "under" the dock, but is it not has consistent (still very easy to reproduce in a few seconds).