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

Issue 708001 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Excessive CPU Use after Opening Chrome Beta

Reported by erig...@gmail.com, Apr 4 2017

Issue description

Steps to reproduce the problem:
1. Open URL (www.espn.com) in Chrome Beta (58.0.3029.42)
2. Leave Chrome Beta (home screen, another app, turn screen off, etc)

What is the expected behavior?
CPU usage will not be high after leaving Chrome.

What went wrong?
Pixel XL running Android 7.1.1 and 7.1.2

I typically run Tugabrowser but have trouble logging in to some sites so I switch to Chrome for those. Within the past few versions of Chrome Beta, once I leave Chrome my phone has felt warm to the touch. Using the System app to monitor system resources I see that the CPU usage remains around 50% when it typically sits at under 5% when I'm doing nothing with the phone. This appears to only occurs after I have opened Chrome. I can sometimes get the phone to idle properly by force closing Chrome Beta but it isn't a guaranteed fix. Rebooting the phone appears to be a consistent fix for this problem.

This does not occur after using the current stable release, Chrome 57.0.2987.132

Did this work before? Yes 57.0.2987.132

Chrome version: 58.0.3029.42  Channel: beta
OS Version: 7.1.2
Flash Version:
 
Cc: msrchandra@chromium.org
Labels: Needs-triage-Mobile Triaged-Mobile Needs-Feedback
Tested the issue on Chrome Stable# 61.0.3163.98 / 62.0.3202.73 & Chrome Canary# 64.0.3251.0 on Pixel (Android 8.0.0 / OPR1 170623.027) and Pixel XL (Android 7.1.2 / N2G48E) and could not reproduce the issue.

@erigion -- Could you please upgrade to latest versions available and update the behavior, if reproducible provide us screen cast of the issue which would help us in triaging the issue further.
Thanks in Advance.
Status: WontFix (was: Unconfirmed)
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

Sign in to add a comment