Dragging icons in launcher is slow until shell restarted

First gif was with 3 screens attached (internal panel and two 1080p screens). This gif is with the laptop screen only enabled (laptop removed from dock)

Finally this gif is after alt-f2, r.

It looks like this might be related to the bubble menu pointer lingering. I can't seem to reproduce it yet.

Any hints on when/how it starts happening?

Seems to happen after a couple of days uptime of the shell.

I am also seeing the little triangle pointer lingering both on the indicator area, but not seen it that I recall on the dock.

I have a bunch of things favourited apps (see screenshot) but nothing out of the ordinary - as in not a ton of things.

Is there some way I can get debug logs or traces from the extension?

I don't know if it's related, but I frequently add and remove external displays. Maybe a couple of times a day. I plug it into the docking station when I work. When I do, the shell freaks out a bit and then settles down. I wonder if the dock is not handling the rapid change in screen resolution well?

As a separate test I have reproduced this on my X220 which has now got an uptime of 3 days with zero applications running besides gnome terminal. When originally booted it was fast as expected. But now, after a number of lock/unlock cycles and 3 days uptime, it's slow to move icons around the launcher.

Status changed to 'Confirmed' because the bug affects multiple users.

It sounds like this is a consequence of some kind of leak in the gnome-shell process. But that does not mean ubuntu-dock is the cause of the leak, it could be anything in gnome-shell.

Can you please keep an eye on the "Vm" values in /proc/PID/status for gnome-shell, as well as the number of entries in /proc/PID/fd/ Tell us if any grow consistently over time and by how much, doing what...

This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 67ubuntu19.10.1

---------------
gnome-shell-extension-ubuntu-dock (67ubuntu19.10.1) eoan; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * utils: Use GObject.NotImplementedError for such errors
  * utils: Allow to pass flags to SignalsHandler's
  * locations: Handle Trash Errors
  * locations: Ensure volume monitor is destroyed on destruction
  * dash: Destroy Removables and Trash if disabled
  * DockManager: Keep a fm1Client reference and destroy it when unneeded
  * docking: Use CONNNECT_AFTER for mounts changes in docked dash
  * dash: Remove the show label timeout if actor got destroyed
  * windowPreviewMenuItem: Disconnect to signals on destroy
  * cleanup: Replace Mainloop functions with GLib ones
  * DashSlideContainer: Inherit from St.Bin instead of widget
  * MyAppIcon: Inherit from Dash.DashIcon (LP: #1846477, #1847102)
  * debian/control: Depend on gnome-shell 3.34.0

  [ Michele Gaio ]
  * Fix a regression due to variable renaming.
  * New upstream release (v67).

  [ Twille ]
  * add missing translation

  [ Philip Langdale ]
  * dash: Add Trash Icon
  * dash: Add Removable drive/device icons
  * prefs: Add prefs to toggle showing Trash and Mounted Volumes
  * appIcons: Implement window tracking for removable devices and trash
  * fileManager1API: Deduplicate window with related locations in tabs
  * locations: Fix a remaining use of `nautilus` vs `gio open`

  [ sicklylife.jp ]
  * Update Japanese translation.

 -- Marco Trevisan (Treviño) <email address hidden> Wed, 09 Oct 2019 17:30:41 +0200

Hmm, OK. Marco says his fix was related to this bug.

To avoid confusion, if it reappears then please open a new bug with information answering comment #9.