wallpaper_resizer.cc hogs CPU and cause chrome to fail liveness check |
||
Issue descriptionExample crash: http://crash/b10b485c9b9b6f7d chrome.txt has "top" output when chrome gets killed, which uses 106.2% CPU. And threads shows it is busy resizing the wallpaper. The resizing task has USER_BLOCKING priority. It seems making chrome super busy and causing UI thread to not responsive. We should consider lower it to USER_VISIBLE (or even BEST_EFFORT). And I wonder whether it makes sense to defer it a big after immediate sign-in, when there are many tasks running.
,
Nov 30
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b4c77a952469bba2a71a17bb08a738cb84bab41a commit b4c77a952469bba2a71a17bb08a738cb84bab41a Author: Wenzhao Zang <wzang@chromium.org> Date: Fri Nov 30 17:53:28 2018 cros: Lower the priority for wallpaper controller task runner Bug: 910409 Change-Id: I7c9a65ccb5e6eb11e2e3f600cef3ba13fe37ee82 Reviewed-on: https://chromium-review.googlesource.com/c/1356240 Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org> Cr-Commit-Position: refs/heads/master@{#612692} [modify] https://crrev.com/b4c77a952469bba2a71a17bb08a738cb84bab41a/ash/wallpaper/wallpaper_controller.cc
,
Dec 4
|
||
►
Sign in to add a comment |
||
Comment 1 by wzang@chromium.org
, Nov 30