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

Issue 766011 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Using google maps often 100%'s my CPU

Reported by jard...@gmail.com, Sep 17 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome
2. Go to google maps.
3. Drag the map around while zooming in/out.  
4: Check your CPU usage

What is the expected behavior?
For it not to stutter and not consume a whole CPU core (I'm running a 4690K)

What went wrong?
It started slowing down on Windows and Linux around Sept 15 2017. I've attached a video that explains the issue in greater detail. 

Did this work before? N/A 

Chrome version: 61.0.3163.79  Channel: stable
OS Version: Ubuntu 16.04
Flash Version: 

Tried disabling the extensions. Same issue.  
Here's a video : https://www.youtube.com/watch?v=yn56lRtjbhE&feature=youtu.be
 
Labels: Needs-Triage-M61
Cc: susanjuniab@chromium.org
Labels: Needs-Feedback
jardayn@ thanks for the issue..

Unable to reproduce this issue on Ubuntu 14.04 using the latest Stable 61.0.3163.91 and latest Dev 63.0.3218.0 with the below steps,

1. Launched Chrome and navigated to https://www.google.co.in/maps
2. Launched the System Monitor -> Resources and observed the CPU History.
3. Zoom in/out on the maps page and can observe that the CPU didn't touch the 100% mark on CPU history.

Please find the attached screen cast and confirm if anything is missed here.

Also request you to retry this issue on a the latest Chrome profile without any flags/extensions and update the thread if the issue still exists.

Thanks..


766011.webm
12.7 MB View Download
Status: WontFix (was: Unconfirmed)
Closing due to lack of feedback requested but not provided. If this issue still exists please open a new issue with the details requested.

Sign in to add a comment