New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 919333 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug


Show other hotlists

Hotlists containing this issue:
Launcher-Broken


Sign in to add a comment

Constant refresh of thumbnails causes 100% browser process CPU usage and increasing memory use

Project Member Reported by nyquist@chromium.org, Jan 6

Issue description

Chrome Version: 72.0.3626.30 (Official Build) dev (64-bit)
Chrome OS Version: 11316.35.0 (Official Build) dev-channel eve, Google_Eve.9584.174.0
Chrome OS Platform: Google Pixelbook
Network info: Google WiFi

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Log in with my personal account
Optional extra step (2): Open shelf

Expected Result:
More or less no CPU usage and no jank. 

Actual Result:
The browser process constantly uses 100% CPU, even while I'm doing nothing.
After the optional step (2), I can see that the thumbnail icons are constantly refreshing right below the search box.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
With my account's current state, this is 100% reproducible on my Pixelbook with my personal account, but not reproducible with my corp account. 

What is the impact to the user, and is there a workaround? If so, what is
it?
The impact is an extremely laggy user experience. I do not know of a workaround.
I have tried deleting my personal account from the device and logging in again, but the problems arised again once sync was finished.

Please provide any additional information below. Attach a screen shot or
log if possible.

---
From looking at chrome://tracing (gathering everything available), it looks like the Chromebook is constantly decoding images. I have attached a full trace. It's of looking at chrome://tracing for a few seconds, then opening the shelf, dragging up the shelf to full screen, waiting for a few seconds, before minimizing the shelf again.

When I open the the bottom shelf, it constantly refreshes the thumbnails. See attached video for the refreshing thumbnails.

The memory for the browser process is constantly increasing while logged in, and the data decoder process seems to always be doing something.
 
trace_constantly-decoding-images.json.gz
6.5 MB Download
VID_20190105_160444.mp4
8.0 MB View Download
cpu-usage.png
124 KB View Download
Components: Services>Sync
This seems to be related to syncing apps. I've removed and added the account a bunch of times to my Chromebook now, and it's only when I start syncing the Apps datatype. I've tried with all the other data types enabled, but without Apps, and it does not happen.
Cc: kaznacheev@chromium.org
Labels: M-72
Owner: khmel@chromium.org
Status: Assigned (was: Unconfirmed)
+khmel for sync and kaznacheev for possibly icon decoding issue.
Could you please attache feedback report or logs from your device? (alt+shift+i or chrome://net-internals/#chromeos -> Store Debug logs)
Thanks
This also can be dup of which was fixed in b/121365016 in 11316.40.0+.

Components: -UI>Shell>Shelf
Doesn't seem related to the shelf?
My apologies. It was almost impossible to comfortably use my chromebook, so I ended up trying to fix it locally. Apparently, deleting a few Android apps helped out, and then going through a few hoops to ensure this was correctly synced to my account.

I am therefore unable to do alt-shift-i or chrome://net-internals/#chromeos :-( I should've thought about that before. I'll definitely do that if the problem pops up again.

From looking at the trace, it was a whole lot of
[{src_file: "../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/image_decoder.cc",
  src_func: "DecodeImage"}]
{src_file: "../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/ui/app_list/arc/arc_app_icon.cc",
  src_func: "LoadForScaleFactor"}]
So it sounds reasonable that the bug khmel@ linked to is related.
Status: Fixed (was: Assigned)
Ok, let close this as duplicate b/121365016. In case you can repro this in builds 11316.40.0, please reopen it.
Thank you for attention and sorry for troubles you faced.

Sign in to add a comment