Steve, IIRC this crash was fixed by *either* the gnome-shell or extension fix. So the original test case would fail only while *neither* of the two fixes were applied.
The gnome-shell fix made the shell API more robust so as to protect itself from crashing in the presence of a buggy extension. The gnome-shell-extension-desktop-icons fix corrects the buggy extension. This is still worthwhile because it fixes a sudden and unnecessary spike of memory and CPU usage from unthrottled timer duplication. That IIRC could still cause instability in the extension/shell based on my memory of testing a year ago. However I've tried stress testing both with and without the fix on focal today and can't see any practical difference in performance. Only technically we shouldn't declare the fix as "released" until the series file is corrected to apply the patch. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
