Issue metadata
Sign in to add a comment
|
High CPU usage on new tab page with custom background while signed in
Reported by
lfu...@gmail.com,
Oct 25
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: 1. Sign in to Sync 2. Use a custom background in new tab page (the custom background can be either an image from the new Chrome Backgrounds feature or just a plain color from some theme). 3. Open new tab page and idle on it. 4. Check CPU usage of new tab process. What is the expected behavior? The New Tab page processshould use ~0% (not different than with no customized background) while idling. What went wrong? The process continuously uses about 5-10%. Did this work before? Yes 68 Chrome version: 70.0.3538.67 Channel: n/a OS Version: 10.0 Flash Version: This started happening on v69 with the revamped New Tab page. It happens only after I'm signed in to Sync and the browser has loaded some user data. Still happens when all extensions are disabled. Tested on 2 computers on both Chrome (69 and 70) and Chromium (69 and 70).
,
Oct 26
lfuser@ Thanks for the issue. Tested this issue on Windows 10 on the reported version 70.0.3538.67, latest Stable 70.0.3538.77 and the latest Canary 72.0.3591.0 and unable to reproduce the issue by following the below steps. 1. Launched Chrome -> signed into Chrome and synced the account. 2. On a new tab page, added a background from new Chrome Background feature. 3. Launched the Task Manager and could observe that CPU usage is ~0% for the New tab page. Attached is the screen cast for reference. Request you to check and confirm if anything is missed from our end in triaging the issue. Also request you to retry the issue by updating Chrome to the latest Stable 70.0.3538.77 and update the thread with the observations. Thanks..
,
Oct 26
Dear Susan, Attached is a video demonstrating reproduction of the issue. I need to correct something: I'm now able to reproduce the issue without signing in to Sync and with an absolutely clean install of Chrome. Not sure why it wouldn't happen before without signing in. Video was recorded on a VM with a clean Windows 10 install, with a freshly installed Chrome 70.0.3538.77. Note: Pointer is not shown, but I'm keeping it still when focused on task manager. Naturally I'm able to reproduce this on my main system (both Chrome and Chromium). I just wanted to rule out all possible variables by running on a clean environment.
,
Oct 26
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 29
lfuser@ Thanks for the update. Re-tested this issue on Windows 10 on the latest Stable 70.0.3538.77 and Canary 72.0.3595.0 and unable to reproduce the issue. On following the steps as per the attached screen cast in comment #6, couldn't observe any increase in CPU. Attached is the screen cast for reference. As this issue is not reproducible at TE end, removing 'Needs-Bisect' label and requesting 'Internals>Core' team to look into the issue and help in further triaging. Thanks..
,
Nov 3
Well, if there's anything else I can do to help figuring this out let me know. I have this happening to me consistently on two computers + VMs. I wouldn't mind giving you a full memory dump or something from it running on the VM. Regards
,
Nov 9
As this issue isn't getting reproduced from our end (...c#2 & c#7) hence adding label "TE-NeedsTriageHelp" and requesting someone from respective team to help in further triaging it. Thanks! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Oct 26