X11/gnome-shell segfault in libmutter-clutter

[AGI-chandler]

Describe the bug
In a GNOME/X11 session with Unite enabled, every time I launch Chrome, about 15 seconds later it causes a segfault in libmutter-clutter with a message like:
gnome-shell[108969]: segfault at 55e00ff32513 ip 00007fce76240a56 sp 00007fff790b8e00 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7fce76209000+8a000] likely on CPU 1 (core 1, socket 0)
Chrome is killed and, because this is an X11 session, gnome-shell is restarted.
Starting Chrome is not the only thing that triggers the fault, but lately it's the only app I've found the reliably reproduces the fault each time.

To Reproduce
Steps to reproduce the behavior:

1. git clone

2. current dconf settings:

   [/]
   app-menu-ellipsize-mode='end'
   app-menu-max-width=0
   autofocus-windows=false
   desktop-name-text='x1g4'
   extend-left-box=true
   greyscale-tray-icons=false
   hide-activities-button='always'
   hide-app-menu-icon=false
   hide-window-titlebars='always'
   notifications-position='center'
   reduce-panel-spacing=true
   restrict-to-primary-screen=true
   show-appmenu-button=true
   show-desktop-name=false
   show-legacy-tray=true
   show-window-buttons='always'
   show-window-title='always'
   use-activities-text=false
   window-buttons-placement='last'
   window-buttons-theme='breeze'
   

3. Launch Chrome (from google-chrome-stable)

4. Wait about 15 seconds, segfault happens

Expected behavior
Chrome stays open.  I don't even care about the segfault but it probs shouldn't happen either.

Environment (please complete the following information):

• OS: Debian 14/15
• GNOME Shell version: 48.4
• Unite version: Current master branch with Commit e26ce42

Logs
At the time of faults, there are messages like the following, however i see these messages occurring at various other times, maybe related to unlocking the screen?
gnome-shell[108969]: Can't update stage views actor unnamed [Gjs_unite_hardpixel_eu_buttons_UniteTrayIndicator] is on because it needs an allocation.

Since about May, I can see journal entries where the segfault happens after starting Chrome:

May 09 08:40:33 x1g4 systemd[718339]: Started app-com.google.Chrome-3600474.scope.
May 09 08:40:47 x1g4 kernel: gnome-shell[3465251]: segfault at 557547291c8d ip 00007f4aa2aa6a06 sp 00007ffe95956e80 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7f4aa2a6f000+8a000] likely on CPU 2 (core 0, socket 0)
May 09 08:42:27 x1g4 systemd[718339]: Started app-com.google.Chrome-3601884.scope.
May 09 08:42:41 x1g4 kernel: gnome-shell[3600741]: segfault at 56438e05df98 ip 00007f14b31e7a06 sp 00007ffc29070b50 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7f14b31b0000+8a000] likely on CPU 2 (core 0, socket 0)
May 09 08:45:00 x1g4 systemd[718339]: Started app-com.google.Chrome-3603720.scope.
May 09 08:45:15 x1g4 kernel: gnome-shell[3602290]: segfault at 55d2c0d3339a ip 00007fe78d604a06 sp 00007fff024050c0 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7fe78d5cd000+8a000] likely on CPU 0 (core 0, socket 0)
May 19 13:49:15 x1g4 systemd[718339]: Started app-com.google.Chrome-1429530.scope.
May 19 13:49:30 x1g4 kernel: gnome-shell[1415968]: segfault at 5645ce6e6a6d ip 00007f2a92e04a06 sp 00007ffd22210520 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7f2a92dcd000+8a000] likely on CPU 1 (core 1, socket 0)
May 19 14:01:12 x1g4 systemd[718339]: Started app-com.google.Chrome-1437412.scope.
May 19 14:01:27 x1g4 kernel: gnome-shell[1429854]: segfault at 5603e2d7b6cd ip 00007fdea0e68a06 sp 00007ffca1a83c60 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7fdea0e31000+8a000] likely on CPU 3 (core 1, socket 0)
May 19 14:01:56 x1g4 systemd[718339]: Started app-com.google.Chrome-1438547.scope.
May 19 14:02:11 x1g4 kernel: gnome-shell[1437884]: segfault at 5566df0a7229 ip 00007fde4b2a6a06 sp 00007ffcc78b20e0 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7fde4b26f000+8a000] likely on CPU 0 (core 0, socket 0)
May 19 14:03:44 x1g4 systemd[718339]: Started app-com.google.Chrome-1440112.scope.
May 19 14:03:59 x1g4 kernel: gnome-shell[1438953]: segfault at 55bc39ec9f99 ip 00007ffa75bbfa06 sp 00007fff512a3c40 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7ffa75b88000+8a000] likely on CPU 0 (core 0, socket 0)
May 19 14:12:18 x1g4 systemd[718339]: Started app-com.google.Chrome-1446962.scope.
May 19 14:12:33 x1g4 kernel: gnome-shell[1440500]: segfault at 5567e7e55170 ip 00007f3a5fea6a06 sp 00007ffe51c67680 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7f3a5fe6f000+8a000] likely on CPU 1 (core 1, socket 0)
May 19 14:13:02 x1g4 systemd[718339]: Started app-com.google.Chrome-1448063.scope.
May 19 14:13:17 x1g4 kernel: gnome-shell[1447390]: segfault at 555f8fbd1cff ip 00007fe8b50a6a06 sp 00007ffd7975be30 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7fe8b506f000+8a000] likely on CPU 1 (core 1, socket 0)
May 19 14:13:29 x1g4 systemd[718339]: Started app-com.google.Chrome-1448893.scope.
May 19 17:14:08 x1g4 kernel: gnome-shell[1448453]: segfault at 563382e5c5d2 ip 00007f1efe9bfa06 sp 00007fff0a50dce0 error 4 in libmutter-clutter-16.so.0.0.0[63a06,7f1efe988000+8a000] likely on CPU 3 (core 1, socket 0)
Jul 10 03:23:27 x1g4 systemd[3635]: Started app-com.google.Chrome-2945571.scope.
Jul 10 03:23:36 x1g4 kernel: gnome-shell[80127]: segfault at 556e2381eb00 ip 00007f6279a41a56 sp 00007ffe65a35950 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7f6279a0a000+8a000] likely on CPU 0 (core 0, socket 0)
Jul 11 12:14:14 x1g4 systemd[3635]: Started app-com.google.Chrome-3735145.scope.
Jul 11 12:14:28 x1g4 kernel: gnome-shell[2945811]: segfault at 55e13c5417bc ip 00007f618a6a4a56 sp 00007ffe85f54040 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7f618a66d000+8a000] likely on CPU 1 (core 1, socket 0)
Jul 11 12:15:23 x1g4 systemd[3635]: Started app-com.google.Chrome-3736491.scope.
Jul 11 12:15:38 x1g4 kernel: gnome-shell[3735478]: segfault at 558334820f5a ip 00007fd055866a56 sp 00007ffcf89c1040 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7fd05582f000+8a000] likely on CPU 2 (core 0, socket 0)
Jul 12 06:40:29 x1g4 systemd[3635]: Started app-com.google.Chrome-355378.scope.
Jul 12 06:40:43 x1g4 kernel: gnome-shell[4029628]: segfault at 557dd9ceb183 ip 00007f6063aa4a56 sp 00007fff561f95c0 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7f6063a6d000+8a000] likely on CPU 3 (core 1, socket 0)
Jul 15 12:06:04 x1g4 systemd[3635]: Started app-com.google.Chrome-3092672.scope.
Jul 15 12:06:16 x1g4 kernel: gnome-shell[2280259]: segfault at 55f8ae20594a ip 00007fa11c52fa56 sp 00007ffd9d34ab70 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7fa11c4f8000+8a000] likely on CPU 2 (core 0, socket 0)
Jul 15 12:06:35 x1g4 systemd[3635]: Started app-com.google.Chrome-3093429.scope.
Jul 15 12:06:47 x1g4 kernel: gnome-shell[3092934]: segfault at 5653da3d4 ip 00007f97b88a4a56 sp 00007ffd972e2400 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7f97b886d000+8a000] likely on CPU 2 (core 0, socket 0)
Jul 22 13:02:06 x1g4 systemd[3635]: Started app-com.google.Chrome-279787.scope.
Jul 22 13:02:19 x1g4 kernel: gnome-shell[3754529]: segfault at 55766fb3517f ip 00007f53e6803a56 sp 00007ffcf4fada80 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7f53e67cc000+8a000] likely on CPU 3 (core 1, socket 0)
-- Boot bdb13ddf33bf44b08a834a1f5fa823eb --
Aug 15 13:01:59 x1g4 systemd[3511]: Started app-com.google.Chrome-3699628.scope.
Aug 15 13:02:12 x1g4 kernel: gnome-shell[3560351]: segfault at 55f64914a ip 00007f859e2a3a56 sp 00007ffc12061820 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7f859e26c000+8a000] likely on CPU 2 (core 0, socket 0)
Aug 15 13:03:03 x1g4 systemd[3511]: Started app-com.google.Chrome-3701017.scope.
Aug 15 13:03:18 x1g4 kernel: gnome-shell[3700029]: segfault at 561746344117 ip 00007fe12c7e0a56 sp 00007ffcfa2e50b0 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7fe12c7a9000+8a000] likely on CPU 0 (core 0, socket 0)
Aug 15 13:03:35 x1g4 systemd[3511]: Started app-com.google.Chrome-3701919.scope.
Aug 15 13:03:50 x1g4 kernel: gnome-shell[3701419]: segfault at 558894da4471 ip 00007fe1014a3a56 sp 00007ffe4b242770 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7fe10146c000+8a000] likely on CPU 3 (core 1, socket 0)
-- Boot 6c9b9763b15148bcbf472e0d7f34cf76 --
Aug 18 20:35:10 x1g4 systemd[3625]: Started app-com.google.Chrome-2040568.scope.
Aug 18 20:35:24 x1g4 kernel: gnome-shell[1645929]: segfault at 564f6dc05079 ip 00007feaba9e2a56 sp 00007ffead3a62e0 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7feaba9ab000+8a000] likely on CPU 1 (core 1, socket 0)
Aug 18 20:42:48 x1g4 systemd[3625]: Started app-com.google.Chrome-2046773.scope.
-- Boot 442218f54d30446dbf332e5f7b6ab742 --
Aug 19 00:30:49 x1g4 kernel: gnome-shell[3782]: segfault at 55c41332b2c0 ip 00007f4a89063a56 sp 00007fffef8d37e0 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7f4a8902c000+8a000] likely on CPU 1 (core 1, socket 0)
Aug 19 00:33:42 x1g4 systemd[3521]: Started app-com.google.Chrome-101658.scope.
Aug 19 00:33:56 x1g4 kernel: gnome-shell[99051]: segfault at 561d2c17c7c4 ip 00007f2d23ea3a56 sp 00007ffe2ed3fc10 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7f2d23e6c000+8a000] likely on CPU 2 (core 0, socket 0)
Aug 19 00:42:06 x1g4 systemd[3521]: Started app-com.google.Chrome-108746.scope.
Aug 19 00:42:21 x1g4 kernel: gnome-shell[101915]: segfault at 55e146eb5a2c ip 00007fc8b2aa3a56 sp 00007ffd17593120 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7fc8b2a6c000+8a000] likely on CPU 0 (core 0, socket 0)
Aug 19 02:19:39 x1g4 systemd[3521]: Started app-com.google.Chrome-183355.scope.
Aug 19 02:19:54 x1g4 kernel: gnome-shell[108969]: segfault at 55e00ff32513 ip 00007fce76240a56 sp 00007fff790b8e00 error 4 in libmutter-clutter-16.so.0.0.0[63a56,7fce76209000+8a000] likely on CPU 1 (core 1, socket 0)

Additional context
Issue has been happening for several months through various gnome-shell and libmutter-clutter versions.  Previously, it seemed after a few crashes, I could eventually get Chrome to stay open after the gnome-shell restart, but now it seems more permanent and blocking.  Now that I figured Unite is involved, I tried disabling it, then starting Chrome, then re-enabled it, which seemed to work initially, but maybe also led to even more instability some time later and I had to just reboot the system... I don't know, could have been caused by latest Debian updates pending a reboot, too... more testing could be done to find a workaround but also have a lot of workspaces open and not much time.