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

Issue 755099 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Hotlist-ChromeExpert


Sign in to add a comment

Loading terribly slow, lots of memory and IO usage

Reported by azar.asg...@live.com, Aug 14 2017

Issue description

Chrome stutters heavily on my HP laptop since forever, especially while scrolling or any animation/effect plays. Mostly everything is stuttering and feels extremely heavy, meanwhile MS Edge does not have any issues. I have enabled GPU rasterization; forced chrome to use the GPU, to no avail. I tried downscaling down to 1080p, which feels incomparably better but then the whole system starts looking blurry/fuzzy on the display. Reinstalling the OS from scratch did not help either. Please help.

System: Chrome 60 on Windows 10 (1703 build)
CPU: i7 6500U
GPU: GTX 950M
RAM: 16GB
Display: 3840x2160
Disk: SSD

 
trace_Mon_Aug_14_2017_1.10.14_PM.json.gz
13.9 MB Download
Cc: kenjibaheux@chromium.org erikc...@chromium.org brucedaw...@chromium.org azar.asg...@live.com
Labels: -Performance Performance-Loading Performance-Memory Performance-Power OS-Windows Pri-2
Summary: Loading terribly slow, lots of memory and IO usage (was: Speed: )
There's a tab entitled "uBlock Origin" that looks very busy. Try closing that and trying again. Adding some more folks and updating the title to help.
Thank you for your reply. Alongside the said extension, I tried disabling all others as well but didn't help and still had the same problem. Note that I've got the same extension on MS edge which runs very smooth even under load.
Looking at the original trace I see that "Photo - Google Photos" is extremely busy.

As was mentioned earlier the uBlock Origin tab was quite busy - it was repeatedly running one second tasks tagged as "VoiceProcessThread". I also saw repeated garbage collection on one tab. It was spending ~80 ms doing the garbage collection, but only 2 ms of that was CPU time. I'm not sure if that means that your machine's CPU was saturated, or if something else was causing this behavior. The garbage collection cycles were happening regularly but weren't collecting much.

With 16 GB of RAM and an SSD it is unlikely that memory pressure is a problem. Your CPU has two cores and four threads so CPU overloading may be an issue, especially if any other programs on your computer are consuming significant CPU. I would recommend looking at the Windows Task Manager's Performance tab to see how busy the CPU is. If it is significantly busy (more than ~40-50%) then it's important to know who is using the CPU time - Chrome or others.

If Chrome is the main consumer of CPU time then Chrome's task manager can more easily show you which tabs are consuming CPU time. Sometimes a greedy page will consume enough CPU time to starve other pages.

I have also seen cases where Chrome's multi-process architecture confuses Windows' CPU performance calculations. This leads to Windows running the CPUs at a low clock speed even though they are running a CPU bound task. You can test this by setting your laptop to the "High performance" power mode to see if it makes any difference.

Comment 4 by grt@chromium.org, Aug 31 2017

Hi Bruce. Is there anything actionable here? Should this have Needs-Feedback or be rolled into another bug?
I had replied to Bruce for his comment, but for some reason it hadn't posted. I did it by replying to the mail as it was mentioned that "Reply to this email to add a comment." Just saw that it hadn't posted. Here is the message:

Thanks for your reply.
 
G Photos was indeed busy because that was the website I was testing the performance on. However, this is not the only site as the issue happens on most websites. I have got an i5-4210U laptop nearby with 8GB RAM and SSD but 1366x768 screen, and Chrome feels way smoother on it.
 
I just tried running the same page with high performance mode, disabling all extensions, quitting all other windows apps and chrome tabs.
Here are some screenshots of my task managers:
Windows Task Manager: http://imgur.com/a/VY1Nt (without high performance mode)
Chrome Task Manager (with all extensions enabled): http://imgur.com/a/NzKin
Chrome Task Manager (with all extensions disabled): http://imgur.com/a/kOLXL
 
It made no visible difference to me by enabling and disabling all my 9 extensions as well as enabling high performance mode.
And my task manager seems to indicate that there is indeed nothing major eating up my CPU in the background.
And the reason why I am so sure that the issue is more with my screen resolution, and not with anything else, is the fluidity I get with Chrome when I downscale my screen resolution to 1920x1080 and it becomes like any other computer. I would happily use that daily, however everything becomes blurry/fuzzy on the display, as I have mentioned before.
 
Cheers,
Azar.
 
It does feel like there is something going on here, but it's hard to tease it out.

The Chrome Task Manager shows that Chrome was relatively idle when you grabbed the screen shot. However the trace showed Google Photos was very busy - consuming lots of CPU time. I suspect that the Task Manager screenshot is from a time when the issue was not reproing. It is important to watch task manager while you repro the bug - while you scroll around for instance.

Since you know how to make the bug appear/disappear (change screen resolution) you can perform tests to better understand what is going on, while monitoring Chrome's task manager. Note that Chrome's task manager shows CPU time as a percentage of total-time available. So, if you have a four-thread/eight-core machine then 12.5% represents a page which is using all of one logical core, and 25% represents a page that is using all of two logical cores. Getting a sense of how much CPU various chrome processes use when the bug is happening would be useful, especially when compared to how much CPU those processes use when the bug is not happening.

It is possible that your GPU is not fast enough for the screen resolution and for what we are asking it to do. Many laptops have two GPUs and it may be that Edge is using the discrete GPU while we are not.

But, the first step would be monitoring CPU usage while reproing the scenario that causes the lag/slowdown, on both high and low resolutions.

The next step is probably to record a pair of ETW traces, one in high and the other in low resolution, as described at https://randomascii.wordpress.com/2015/09/01/xperf-basics-recording-a-trace-the-ultimate-easy-way/, and then share those with me.

For all of these investigations it is helpful to keep the scenario as simple as possible to avoid distractions. Therefore, having a single tab and no extensions is very helpful. Otherwise we may get distracted or confused by activity in the extensions and other tabs.

azar.asgarov@,
Could you please check this issue as per c#6 & update the thread accordingly.
Thanks..!!
Labels: Needs-Feedback
Hi. I don't want to sound rude, but I just don't have time nor interest for this. This had been taking more than a month now, and it's clearly Google's problem. If they or their experts cannot simulate and fix the problem, it's not the users' issue. Just to check that I wasn't the only one, I've tested this on another laptop with 4K and same CPU, and had the same issues. So it's clearly Google at fault since even Photoshop runs smoother with 4K screen. 
I have another problem with Google's another product, and the help forums and those experts were of zero help too. Regardless of how many people had the same issue, Google is either unable to fix the issue or issued aren't at their interest at all.
Thank you for your time.
Project Member

Comment 10 by sheriffbot@chromium.org, Sep 13 2017

Cc: jmukthavaram@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 11 by ajha@chromium.org, Oct 25 2017

Labels: TE-NeedsTriageHelp
Status: WontFix (was: Unconfirmed)

Sign in to add a comment