Please push out a fix for this ASAP, once this tight loop is hit the machine becomes an unusable 100% CPU using mess. I know of several others suffering exactly the same bug.
For me this can be reproduced by having a terminal using half the screen (using CMD+LEFT), then switching to fullscreen (F11) and back (F11). Repeating this some number of times triggers this tight loop of 100% CPU usage. After that, it's difficult to get window focus and windows are slow to respond to anything. To recover I use `killall -3 gnome-shell`, which allows Gnome to restart but then has the delightful affect of throwing windows around the screen randomly and forgetting there are multiple monitors. -- 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/1880405 Title: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
