Public bug reported:
GNOME Shell running in Wayland completely hangs when the key repeat rate
is sufficiently high and used inside Chromium and/or Google Chrome. Then
GNOME Shell, at-spi's dbus-daemon, ibus-daemon, and chromium-browser all
get stuck at 100% CPU. GNOME Shell's RSS also quickly increases to >2GB
and continues climbing.
Attempting to kill chromium-browser in a separate TTY either causes one of two
things:
- gnome-shell, dbus-daemon and ibus-daemon remain at 100% CPU and stuck; or
- gnome-shell temporarily recovers, then crashes, taking the entire session
with it and returning to the login screen.
Steps to reproduce:
1. Set key repeat rates to a high value (these are my actual settings):
$ gsettings set org.gnome.desktop.peripherals.keyboard repeat-interval 3
$ gsettings set org.gnome.desktop.peripherals.keyboard repeat true
$ gsettings set org.gnome.desktop.peripherals.keyboard delay 180
2. Start chromium-browser
3. Focus the location bar in chromium-browser
4. Press and hold a key (e.g. a) for a few seconds (~10 should do)
5. Observe that gnome-shell probably has hung by this point. If it hasn't,
proceed to step 6.
6. Press and hold the backspace button until the location bar has cleared, then
continue for another few seconds (~10 seconds should do)
This also affected GNOME Shell 3.24, but I was able to reduce the chances of it
happening by renicing my chromium processes to +10, thereby giving GNOME Shell
a greater chance at the CPU.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
Uname: Linux 4.13.4-hyper2+ x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Nov 10 16:50:13 2017
DisplayManager: gdm3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-11-04 (5 days ago)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1731420
Title:
gnome-shell hangs (goes into key repeat runaway) when key repeat is
used on chromium-browser's address bar
Status in gnome-shell package in Ubuntu:
New
Bug description:
GNOME Shell running in Wayland completely hangs when the key repeat
rate is sufficiently high and used inside Chromium and/or Google
Chrome. Then GNOME Shell, at-spi's dbus-daemon, ibus-daemon, and
chromium-browser all get stuck at 100% CPU. GNOME Shell's RSS also
quickly increases to >2GB and continues climbing.
Attempting to kill chromium-browser in a separate TTY either causes one of
two things:
- gnome-shell, dbus-daemon and ibus-daemon remain at 100% CPU and stuck; or
- gnome-shell temporarily recovers, then crashes, taking the entire session
with it and returning to the login screen.
Steps to reproduce:
1. Set key repeat rates to a high value (these are my actual
settings):
$ gsettings set org.gnome.desktop.peripherals.keyboard repeat-interval 3
$ gsettings set org.gnome.desktop.peripherals.keyboard repeat true
$ gsettings set org.gnome.desktop.peripherals.keyboard delay 180
2. Start chromium-browser
3. Focus the location bar in chromium-browser
4. Press and hold a key (e.g. a) for a few seconds (~10 should do)
5. Observe that gnome-shell probably has hung by this point. If it hasn't,
proceed to step 6.
6. Press and hold the backspace button until the location bar has cleared,
then continue for another few seconds (~10 seconds should do)
This also affected GNOME Shell 3.24, but I was able to reduce the chances of
it happening by renicing my chromium processes to +10, thereby giving GNOME
Shell a greater chance at the CPU.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
Uname: Linux 4.13.4-hyper2+ x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Nov 10 16:50:13 2017
DisplayManager: gdm3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-11-04 (5 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731420/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
