You are not logged in.

#1 2021-03-27 17:35:30

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Google Chrome timing out on shutdown

Since early March (around the time the AUR package updated to version 89), I have been experiencing a google chrome timeout that hangs whenever I try to reboot/shutdown with chrome open:

Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Stopping timed out. Killing.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Killing process 1873 (chrome) with signal SIGKILL.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Killing process 2192 (ThreadPoolSingl) with signal SIGKILL.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Killing process 1903 (CrShutdownDetec) with signal SIGKILL.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Killing process 1918 (ThreadPoolForeg) with signal SIGKILL.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Failed with result 'timeout'.

This occurs every now and then, with seemingly no regular pattern, and I have not  been able to figure out what the problem is. Prior to March, I have been using chromium for months without ever encountering this issue, but switched to chrome due to chromium no longer supporting sync.

I have tried turning off "Continue running background apps when Google Chrome is closed", but the issue persists.
I have also tried looking online for more solutions, and found the following threads:
https://bbs.archlinux.org/viewtopic.php?id=234280
https://bugs.chromium.org/p/chromium/is … ?id=429404

Though the issues appear to be related, none of them explicitly mention chrome hanging until SIGKILL.

PS:
While this issue only surfaced this month, I have also been experiencing the following behavior on chromium and chrome for a longer period of time:
https://bbs.archlinux.org/viewtopic.php … 4#p1432324

Edit:
Not only is the bug itself not easy to reproduce, but sometimes the error messages in the journal logs change. For example, I recently had a reboot that was delayed by the following:

Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Stopping timed out. Killing.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1044 (chrome) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1666 (ThreadPoolSingl) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1053 (sandbox_ipc_thr) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1092 (chrome) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1097 (HangWatcher) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1098 (ThreadPoolServi) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1100 (ThreadPoolForeg) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1101 (ThreadPoolForeg) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1102 (Chrome_IOThread) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1103 (inotify_reader) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1104 (MemoryInfra) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1107 (gmain) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1108 (gdbus) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1115 (pool-google-chr) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1116 (Bluez D-Bus thr) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1117 (CrShutdownDetec) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1118 (dconf worker) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1119 (ThreadPoolForeg) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1120 (ThreadPoolForeg) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1121 (CompositorTileW) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1122 (VideoCaptureThr) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1123 (ThreadPoolSingl) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1124 (gpu-process_cra) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1126 (CacheThread_Blo) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1127 (BrowserWatchdog) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1128 (utility_crash_u) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1146 (ThreadPoolSingl) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1149 (ThreadPoolForeg) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1150 (ThreadPoolForeg) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1151 (ThreadPoolForeg) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1152 (ThreadPoolForeg) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1162 (n/a) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1229 (n/a) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Killing process 1658 (n/a) with signal SIGKILL.
Mar 27 20:41:14 poxter systemd[424]: app-gnome-lwsm-938.scope: Failed with result 'timeout'.

Last edited by GeneralPoxter (2021-03-28 02:27:38)

Offline

Board footer

Powered by FluxBB