GNOME Bugzilla – Bug 769956
Taking a screenshot of chrome results in hang and 100% cpu usage
Last modified: 2020-11-26 16:11:14 UTC
I've been having issues with gnome-screenshot since updating some gnome packages a few days ago. Interestingly, gnome-screenshot itself was not updated, so I assume this is a side-effect of something else breaking. A bunch of things have gone haywire since this update... For example, nautilus uses 100% of one of my CPUs right at boot until I kill the process. Anyways, sometimes when I try to take a screenshot of an area I never actually get the save dialog, and my gnome-screenshot starts taking 100% of one of my CPUs. It seems to only be an issue when taking a screenshot of a particular tab in Google chrome. I can take screenshots of other applications and even other tabs in Chrome without any problems. I've straced gnome-screenshot during the failure condition and it hangs here: futex(0x1fbb3d0, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x1fbb3c0, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x25a2580, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x1fbb3d0, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x1fbb3c0, FUTEX_WAKE_PRIVATE, 1) = 0 futex(0x1fbb3d0, FUTEX_WAKE_PRIVATE, 1) = 1 mmap(NULL, 111431680, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f821d5bb000 I don't see anything suspicious in the journal... I've also tried with all extensions disabled and still see the same problem. Any ideas what's going on? Here are the gnome applications that were updated. I started noticing the problem after this update: [2016-08-11 11:18] [ALPM] upgraded gnome-online-accounts (3.20.1-1 -> 3.20.3-2) [2016-08-11 11:18] [ALPM] upgraded gnome-session (3.20.1-1 -> 3.20.2-1) [2016-08-11 11:18] [ALPM] upgraded gnome-calculator (3.20.1-1 -> 3.20.2-1) [2016-08-11 11:18] [ALPM] upgraded gnome-characters (3.20.1-1 -> 3.20.1-2) [2016-08-11 11:18] [ALPM] upgraded gnome-code-assistance (3.16.0-4 -> 3.16.1-1) [2016-08-11 11:18] [ALPM] upgraded gnome-color-manager (3.20.0-1 -> 3.20.0-2) [2016-08-11 11:18] [ALPM] upgraded gnome-control-center (3.20.1-1 -> 3.20.1-2) [2016-08-11 11:18] [ALPM] upgraded gnome-dictionary (3.20.0-1 -> 3.20.0-2) [2016-08-11 11:18] [ALPM] upgraded gnome-documents (3.20.0-1 -> 3.20.0-2) [2016-08-11 11:18] [ALPM] upgraded gnome-keyring (1:3.20.0-1 -> 1:3.20.0-2) [2016-08-11 11:18] [ALPM] upgraded gnome-logs (3.20.1-1 -> 3.20.1-2) [2016-08-11 11:18] [ALPM] upgraded gnome-mahjongg (3.20.0-1 -> 3.20.0-2) [2016-08-11 11:18] [ALPM] upgraded gnome-maps (3.20.1-1 -> 3.20.2-1) [2016-08-11 11:18] [ALPM] upgraded gnome-nettool (3.8.1-2 -> 3.8.1-3) [2016-08-11 11:18] [ALPM] upgraded gnome-photos (3.20.2-1 -> 3.20.3-1) [2016-08-11 11:18] [ALPM] upgraded gnome-sudoku (3.20.2-1 -> 3.20.4-1) [2016-08-11 11:18] [ALPM] upgraded gnome-system-log (3.9.90-1 -> 3.9.90-2) [2016-08-11 11:18] [ALPM] upgraded gnome-system-monitor (3.20.1-1 -> 3.20.1-2) [2016-08-11 11:18] [ALPM] upgraded gnome-terminal (3.20.2-1 -> 3.20.2-2) [2016-08-11 11:18] [ALPM] upgraded gnome-tetravex (3.20.0-1 -> 3.20.0-2) [2016-08-11 11:18] [ALPM] upgraded gnome-tweak-tool (3.20.1-1 -> 3.20.1-2)
No additional comment in 4 years ⇒ closing. If this happens again, please feel free to open an issue on GitLab: https://gitlab.gnome.org/GNOME/gnome-screenshot/issues/new