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

Issue 677744 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature



Sign in to add a comment

Enhance Task Manager CPU ranking for GU-consuming tabs

Reported by harald.r...@gmail.com, Jan 1 2017

Issue description

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

Steps to reproduce the problem:
Many web pages reaches a state where high cpu or browser load is used. This causes fan noise and slows down the computer

In the past, the CPU ranking was adequate to indicate the culprit tab so this could be removed from view or killed "End process"
- If a new tab is opened for the browser window, a high-cpu tab is no longer in view and typically stops consuming cpu resources

What is the expected behavior?
Rank by CPU, kill whatever consumes 10% or more that is not Browser or GPU Process
- fan noise stops

Possibly introduce GPU load column or some other means of indicating culprit tab, for example map the Browser/GPU usage back to the causing process like system CPU value in top

What went wrong?
In GNOME/Wayland, some tabs causes high Browser/GPU Process consumption without using the cpu therefore cannot be traced to a single tab. Ie. 50% Browser 25% GPU, fan is running and you have 100 tab suspects getting away with it.

Did this work before? N/A 

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 
Flash Version: 

With version 53+ large tab populations are much more efficient. I have a 50 GiB swap and it is nowadays barely used.
 
Cc: brajkumar@chromium.org
Components: -UI Internals>GPU
Labels: Needs-Feedback
Could you please provide GPU details from chrome://gpu for further investigation.

Thanks!
Cc: harald.r...@gmail.com
Ping harald.rudell@gmail.com for feedback on GPU details from chrome://gpu.

Thank you.
chrome://flags/
Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
VPx Video Decode: Hardware accelerated
WebGL: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
count_all_in_varyings_packing
disable_framebuffer_cmaa
disable_post_sub_buffers_for_onscreen_surfaces
msaa_is_slow
scalarize_vec_and_mat_constructor_args
Problems Detected
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Mesa drivers in Linux handle varyings without static use incorrectly: 333885
Applied Workarounds: count_all_in_varyings_packing
Disable partial swaps on Mesa drivers (detected with GL_RENDERER): 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
Timer queries crash on Intel GPUs on Linux: 540543, 576991
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
Disable partial swaps on Mesa drivers (detected with GL_VERSION): 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Accelerated rasterization has been disabled, either via blacklist, about:flags or the command line.
Disabled Features: rasterization
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers



I use this flag:
Override software rendering list Mac, Windows, Linux, Chrome OS, Android
Overrides the built-in software rendering list and enables GPU-acceleration on unsupported system configurations. #ignore-gpu-blacklist
- otherwise video playback not so good

It's a MacBook Pro 2015 Ubuntu 16.10 GNOME Shell/Wayland

I think i subsequently discovered high cpu related to extensions:
- click to remove element
- tabs outliner

Opening the task manager costs about 18% cpu on the browser process, that seems really high (4 profiles/100 tabs)

My ambition is to have 90%+ idle as reported by top

[attaching a colorful .mhhtml gives me a status code 500 from the bug tool]
170124-c89-chromium-gpuflags.txt
17.9 KB View Download
It’s 2-core hyper threading, ie. 4 cpus, so 18% in column %CPU process value means 4.5% of cpu idle percentage
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 31 2017

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Comment 6 by enne@chromium.org, Jan 31 2017

Components: Tools
Labels: -Type-Bug Type-Feature
Status: Assigned (was: Unconfirmed)

Comment 7 by cda...@chromium.org, Mar 13 2017

Labels: -Needs-Review
Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]
Owner: ----
Status: Untriaged (was: Assigned)

Comment 9 by enne@chromium.org, May 12 2017

Owner: nduca@chromium.org
Status: Assigned (was: Untriaged)
nduca: a feature request for you

Comment 10 by nduca@chromium.org, Jul 20 2017

Owner: ----

Sign in to add a comment