Computer shutdown/reboot takes long time with chrome opened
Reported by
reset...@gmail.com,
Mar 14 2016
|
|||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36
Steps to reproduce the problem:
1. Bootup computer
2. Open chrome
3. Work with some pages
4. Shutdown computer without closing chrome
What is the expected behavior?
Computer must shutdown without delays
What went wrong?
Huge delay (about 2min) waiting for `cat` process created by chrome to be killed by timeout.
...
|-xfce4-panel(690)-+-chrome(938)-+-cat(945)
| | |-cat(946)
| | |-chrome(989)-+-chrome(991)
| | | |-{Chrome_ChildIOT}(993)
| | | |-{SGI_video_sync}(1008)
| | | |-{Watchdog}(992)
| | | |-{WorkerPool/1005}(1005)
| | | `-{handle-watcher-}(994)
| | |-chrome-sandbox(948)---chrome(949)-+-chrome(954)-+-chrome(1001)-+-{Chrome_ChildIOT}(10+
| | | | | |-{CompositorTileW}(10+
| | | | | |-{CompositorTileW}(10+
| | | | | |-{CompositorTileW}(10+
| | | | | |-{CompositorTileW}(10+
...
[ 423.510785] systemd[1]: session-c2.scope: Child 1337 belongs to session-c2.scope
[ 451.565131] systemd[1]: systemd-logind.service: Got notification message from PID 486 (WATCHDOG=1)
[ 452.065135] systemd-journald[207]: Sent WATCHDOG=1 notification.
[ 452.065250] systemd[1]: systemd-journald.service: Got notification message from PID 207 (WATCHDOG=1)
[ 511.565221] systemd[1]: session-c2.scope: Stopping timed out. Killing.
[ 511.565398] systemd[1]: session-c2.scope changed stop-sigterm -> stop-sigkill
[ 511.565563] systemd[1]: Received SIGCHLD from PID 945 (cat).
[ 511.565582] systemd[1]: Child 945 (cat) died (code=killed, status=15/TERM)
[ 511.565613] systemd[1]: session-c2.scope: Child 945 belongs to session-c2.scope
Did this work before? N/A
Chrome version: 49.0.2623.87 Channel: stable
OS Version: 4.4.5-1-zen #1 ZEN SMP PREEMPT Thu Mar 10 12:43:55 UTC 2016 x86_64 GNU/Linux
Flash Version: Shockwave Flash 21.0 r0
This bug occurs in 85-90% tries (not 100%).
,
Mar 27 2016
attached pstree with arguments (`pstree -p 1153 -a > chrome.pstree-with-args.txt`) just before one of the buggy reboot. Also after I've started chrome after reboot it displayed this warning - http://dl1.joxi.net/drive/0011/1977/776121/160327/e821df1779.png
,
Mar 27 2016
I think the problem is near 73 line in chrome startup script.
resetko@resetko ~ $ cat /opt/google/chrome/google-chrome | grep cat -B 2 -A 2 -n
40- # Use system xdg utilities. But first create mimeapps.list if it doesn't
41- # exist; some systems have bugs in xdg-mime that make it fail without it.
42: xdg_app_dir="${XDG_DATA_HOME:-$HOME/.local/share/applications}"
43- mkdir -p "$xdg_app_dir"
44- [ -f "$xdg_app_dir/mimeapps.list" ] || touch "$xdg_app_dir/mimeapps.list"
--
71-# processes ( http://crbug.com/376567 ).
72-exec < /dev/null
73:exec > >(exec cat)
74:exec 2> >(exec cat >&2)
75-
76-# Make sure that the profile directory specified in the environment, if any,
,
Mar 28 2016
Thank you for providing more feedback. Adding requester "rsleevi@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 28 2016
Thanks. Assigned to mdempsky@, as he added the cat commands to the launcher script.
,
Mar 28 2016
If you comment out the
exec > >(exec cat)
exec 2> >(exec cat >&2)
lines, does your computer shutdown/reboot faster?
I won't rule that possibility out, but it seems really unlikely to me. Those cat processes should exit as soon as chrome exits. If they're still around preventing your computer from shutting down / rebooting, then that means Chrome (or an orphaned child process that we failed to kill / cleanup) is still running anyway.
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
,
Aug 1
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rsleevi@chromium.org
, Mar 15 2016