Issue 373489 in chromium: GPU Process uses 70-100% cpu when using google play music

[chro...@googlecode.com]

Status: Untriaged
Owner: ----
Labels: Type-Bug Pri-2 Cr-Internals-GPU OS-Linux

New issue 373489 by ma...@chromium.org: GPU Process uses 70-100% cpu when
using google play music
http://code.google.com/p/chromium/issues/detail?id=373489

Version: Google Chrome 36.0.1985.2 (Official Build 269731) dev
OS: Ubuntu 12.04.4 LTS


What steps will reproduce the problem?
1. open https://play.google.com/music
2. play something
3. open task manager, sort by cpu column

What is the expected output?
Some reasonable amount of cpu usage. Play Music does almost nothing
graphical, using nearly 100% cpu is crazy.

What do you see instead?
GPU process uses nearly 100% cpu any time Play Music is playing (even when
minimized).


Play music only has two animated things on the page:
1) An animated gif next to the playing track.
2) A progress bar at the bottom.


Using devtools to hide the animated gif takes the gpu process cpu usage
down to 10-30%.
Also hiding the progress bar takes the gpu process cpu usage down to <10%.




chrome://gpu info:

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash 3D: Unavailable. Hardware acceleration unavailable
Flash Stage3D: Unavailable. Hardware acceleration unavailable
Flash Stage3D Baseline profile: Unavailable. Hardware acceleration
unavailable
Compositing: Hardware accelerated and threaded.
Rasterization: Software only, hardware acceleration unavailable
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Hardware accelerated
WebGL: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_post_sub_buffers_for_onscreen_surfaces
init_gl_position_in_vertex_shader
init_vertex_attributes
use_current_program_after_successful_link
Problems Detected
Accelerated 2d canvas is unstable in Linux at the moment
Disabled Features: accelerated_2d_canvas
Stage3D is not supported on Linux: 129848
Disabled Features: flash_stage3d
Accelerated video decode is unavailable on Mac and Linux: 137247, 133828
Disabled Features: accelerated_video_decode
NVIDIA linux drivers are unstable when using multiple Open GL contexts and
with low memory: 145600
Disabled Features: flash_3d, accelerated_video_decode, flash_stage3d
GPU rasterization is whitelisted on N4, N5, N7 and Moto X: 362779
Disabled Features: gpu_rasterization
Always call glUseProgram after a successful link to avoid a driver bug:
349137
Applied Workarounds: use_current_program_after_successful_link
Program link fails in NVIDIA Linux if gl_Position is not set: 286468
Applied Workarounds: init_gl_position_in_vertex_shader
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Linux NVIDIA drivers don't have the correct defaults for vertex attributes:
351528
Applied Workarounds: init_vertex_attributes
Disable partial swaps on linux drivers: 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Version Information
Data exported 5/14/2014 3:21:58 PM
Chrome version Chrome/36.0.1985.2
Operating system Linux 3.2.5-gg1336
Software rendering list version 8.4
Driver bug list version 5.3
ANGLE commit id 74697cf2064c
2D graphics backend Skia
Command Line Args
--user-data-dir=/usr/local/google/home/mattm/.config/google-chrome-unstable
--flag-switches-begin --flag-switches-end
Driver Information
Initialization time 155
Sandboxed true
GPU0 VENDOR = 0x10de, DEVICE= 0x0ffe
Optimus false
AMD switchable false
Driver vendor NVIDIA
Driver version 331.67
Driver date
Pixel shader version 4.40
Vertex shader version 4.40
Machine model name
Machine model version
GL_VENDOR NVIDIA Corporation
GL_RENDERER Quadro K2000/PCIe/SSE2
GL_VERSION 4.4.0 NVIDIA 331.67
GL_EXTENSIONS GL_AMD_multi_draw_indirect
GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays
GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended
GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture
GL_ARB_color_buffer_float GL_ARB_compatibility
GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth
GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_copy_buffer
GL_ARB_copy_image GL_ARB_debug_output GL_ARB_depth_buffer_float
GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers
GL_ARB_draw_buffers_blend GL_ARB_draw_indirect
GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced
GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility
GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location
GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport
GL_ARB_fragment_program GL_ARB_fragment_program_shadow
GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments
GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4
GL_ARB_get_program_binary GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64
GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging
GL_ARB_indirect_parameters GL_ARB_instanced_arrays
GL_ARB_internalformat_query GL_ARB_internalformat_query2
GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment
GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect
GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query
GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters
GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex
GL_ARB_robust_buffer_access_behavior GL_ARB_robustness
GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map
GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects
GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding
GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote
GL_ARB_shader_image_load_store GL_ARB_shader_image_size
GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_query_buffer_object
GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine
GL_ARB_shader_texture_lod GL_ARB_shading_language_100
GL_ARB_shading_language_420pack GL_ARB_shading_language_include
GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing
GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_border_clamp
GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32
GL_ARB_texture_buffer_range GL_ARB_texture_compression
GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc
GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array
GL_ARB_texture_env_add GL_ARB_texture_env_combine
GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float
GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge
GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample
GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels
GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg
GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage
GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle
GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2
GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced
GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object
GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object
GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding
GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader
GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev
GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers
GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc
GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform
GL_EXT_blend_color GL_EXT_blend_equation_separate
GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract
GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test
GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced
GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit
GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats
GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object
GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4
GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays
GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels
GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex
GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects
GL_EXT_separate_specular_color GL_EXT_shader_image_load_store
GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap
GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object
GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc
GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc
GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp
GL_EXT_texture_env_combine GL_EXT_texture_env_dot3
GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod
GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object
GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB
GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle
GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array
GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_x11_sync_object
GL_EXT_import_sync_object GL_IBM_rasterpos_clip
GL_IBM_texture_mirrored_repeat GL_KHR_debug GL_KTX_buffer_region
GL_NV_bindless_multi_draw_indirect GL_NV_bindless_texture
GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_compute_program5
GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image
GL_NV_deep_texture3D GL_NV_depth_buffer_float GL_NV_depth_clamp
GL_NV_draw_texture GL_NV_ES1_1_compatibility GL_NV_explicit_multisample
GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program
GL_NV_fragment_program_option GL_NV_fragment_program2
GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4
GL_NV_gpu_program4 GL_NV_gpu_program4_1 GL_NV_gpu_program5
GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5
GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage
GL_NV_multisample_filter_hint GL_NV_occlusion_query
GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object
GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range
GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners
GL_NV_register_combiners2 GL_NV_shader_atomic_counters
GL_NV_shader_atomic_float GL_NV_shader_buffer_load
GL_NV_shader_storage_buffer_object GL_ARB_sparse_texture
GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc
GL_NV_texture_env_combine4 GL_NV_texture_expand_normal
GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader
GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback
GL_NV_transform_feedback2 GL_NV_vdpau_interop GL_NV_vertex_array_range
GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit
GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program
GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option
GL_NV_vertex_program3 GL_NV_video_capture GL_NVX_conditional_render
GL_NVX_gpu_memory_info GL_NVX_nvenc_interop GL_SGIS_generate_mipmap
GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum
Window system binding vendor NVIDIA Corporation
Window system binding version 1.4
Window system binding extensions GLX_EXT_visual_info GLX_EXT_visual_rating
GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_SGI_video_sync GLX_SGI_swap_control
GLX_EXT_swap_control GLX_EXT_swap_control_tear GLX_EXT_texture_from_pixmap
GLX_EXT_buffer_age GLX_ARB_create_context GLX_ARB_create_context_profile
GLX_EXT_create_context_es_profile GLX_EXT_create_context_es2_profile
GLX_ARB_create_context_robustness GLX_ARB_multisample GLX_NV_float_buffer
GLX_ARB_fbconfig_float GLX_NV_swap_group GLX_EXT_framebuffer_sRGB
GLX_NV_multisample_coverage GLX_NV_copy_image GLX_NV_video_capture
Direct rendering Yes
Reset notification strategy 0x8252


Attachments:
trace_playmusic.json.gz 2.0 MB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Cc: rev...@chromium.org en...@chromium.org brian...@chromium.org

Comment #2 on issue 373489 by pi...@chromium.org: GPU Process uses 70-100%

cpu when using google play music
http://code.google.com/p/chromium/issues/detail?id=373489

Keep in mind that it's 100% of one (most likely) throttled core (you can
check the frequency via cpu_freq). The GPU process has to do some work
every frame, in an ideal world it would be at 100% of one core running at
very low frequency. %cpu by itself is not a very good metric these days.

The fact that there are 2 regions that animate mean we have to redraw
everything in the region encompassing all the dirty rects - you can see
with the devtools. When both the animated gif and the progress bar change
in the same frame, the overall dirty rect becomes large.

That page is somewhat complex, and so it takes some amount of CPU to redraw
all that.

That said, it looks like the SGI_video_sync thread is taking a lot of CPU
whereas it should be idle most of the time. Maybe the driver is doing an
active poll instead of a passive one - I don't know.
Currently we're not using the information coming from that thread on linux
(vsync scheduling info), but we eventually will want to. I guess we could
disable it in the short term, but we'll have to figure out how to get that
information later.

[chro...@googlecode.com]

Comment #3 on issue 373489 by pi...@chromium.org: GPU Process uses 70-100%

cpu when using google play music
http://code.google.com/p/chromium/issues/detail?id=373489

re:cpu not going down when minimized, I believe it's because the UI layers
are not notifying the WebContents that it's hidden when the window is
minimized.

[chro...@googlecode.com]

Comment #6 on issue 373489 by gilwoo...@gmail.com: GPU Process uses 70-100%

cpu when using google play music
http://code.google.com/p/chromium/issues/detail?id=373489

I have seen similar problems with the SGI_video_sync thread.
I'm using Version 36.0.1985.32 beta on Fedora 20 (3.14.2-200.fc20.x86_64)
I also have an NVIDA card with NVIDA drivers:
GPU0 VENDOR = 0x10de, DEVICE= 0x0fc1
Driver vendor NVIDIA
GL_VENDOR NVIDIA Corporation
GL_RENDERER GeForce GT 640/PCIe/SSE2

I sometimes have the problem even without playing music on google play.
On my machine it's not reproducible 100% of the time. Sometimes it's stuck
in high CPU usage and closing & reopening some tab makes the problem go
away.
I've seen that happen with play.google.com tabs as well as pdf tabs.

[chro...@googlecode.com]

Comment #8 on issue 373489 by kos...@gmail.com: GPU Process uses 70-100%

cpu when using google play music
http://code.google.com/p/chromium/issues/detail?id=373489

I'm facing the same issue, except that I'm using SOundcloud instead of
Google Play.

[chro...@googlecode.com]

Comment #9 on issue 373489 by kos...@gmail.com: GPU Process uses 70-100%

cpu when using google play music
http://code.google.com/p/chromium/issues/detail?id=373489

I'm facing the same issue, except that I'm using Soundcloud instead of
Google Play.
I thought it was originally caused by some audio driver, since it seems
that high cpu usage only happens when playing music.

[chro...@googlecode.com]

Comment #10 on issue 373489 by owlberte...@gmail.com: GPU Process uses

70-100% cpu when using google play music
http://code.google.com/p/chromium/issues/detail?id=373489

Same here. Starting chromium with --blacklist-accelerated-compositing makes
the CPU usage a lot better.

[chro...@googlecode.com]

Comment #11 on issue 373489 by dark...@gmail.com: GPU Process uses 70-100%

cpu when using google play music

https://code.google.com/p/chromium/issues/detail?id=373489

Just wanted to report that with Chrome 37 stable on Linux using Google Play
Music is still problematic - the only "workaround" I found is to keep the
tab open in a separate window and keep it minimized.

[chro...@googlecode.com]

Comment #12 on issue 373489 by sdmara...@gmail.com: GPU Process uses

70-100% cpu when using google play music
https://code.google.com/p/chromium/issues/detail?id=373489

i have noticed CPU usage goes down if you uncheck "enable hardware
acceleration when available"

[chro...@googlecode.com]

Comment #13 on issue 373489 by dim...@gmail.com: GPU Process uses 70-100%

cpu when using google play music
https://code.google.com/p/chromium/issues/detail?id=373489

this is driving me mad! not sure which version of Chrome this started with,
but CPU usage has been a lot more than in the past even when I'm not
actively browsing. Have about 16 tabs open, which is nothing unusual in the
years I've used Chrome and it's only recently that there are times where I
have to close Chrome just to be able to listen to music.

[chro...@googlecode.com]

Comment #14 on issue 373489 by cox.kath...@gmail.com: GPU Process uses

70-100% cpu when using google play music
https://code.google.com/p/chromium/issues/detail?id=373489

On Ubuntu 14.04, this seems to be an issue with any page that has
animations at all. YouTube (w/ HTML5 videos), hangouts, etc.

[chro...@googlecode.com]

Updates:
Status: Fixed

Comment #21 on issue 373489 by brian...@chromium.org: GPU Process uses

70-100% cpu when using google play music

https://code.google.com/p/chromium/issues/detail?id=373489

@jaxbot: This bug is for Linux only. If you've seen a regression on Mac,
please open a new issue.

I've verified locally that CPU usage has improved, but would like make sure
I didn't fix a different bug. Can anyone who reported seeing this problem
on Linux verify the fix using the directions in #19. Thanks!

[chro...@googlecode.com]

Comment #22 on issue 373489 by jax...@gmail.com: GPU Process uses 70-100%

cpu when using google play music
https://code.google.com/p/chromium/issues/detail?id=373489

Here's the issue I opened a while ago for Mac, if anyone is curious:
https://code.google.com/p/chromium/issues/detail?id=399960

[chro...@googlecode.com]

Comment #24 on issue 373489 by sir...@gmail.com: GPU Process uses 70-100%

cpu when using google play music

https://code.google.com/p/chromium/issues/detail?id=373489

I'm having the same issue. I hope it get fixed. On Chromium 37.0.2062.120
Built on Ubuntu 14.04, running on LinuxMint 17

[chro...@googlecode.com]

Comment #25 on issue 373489 by matthew....@gmail.com: GPU Process uses

70-100% cpu when using google play music
https://code.google.com/p/chromium/issues/detail?id=373489

The latest version of Chrome for Linux is 38.x. You should upgrade to that
and try again. It's gotten much better for me since that release.

[chro...@googlecode.com]

Comment #26 on issue 373489 by ImCoding...@gmail.com: GPU Process uses

70-100% cpu when using google play music
https://code.google.com/p/chromium/issues/detail?id=373489

The problem isn't fixed for me. Im using chromium version 38.0.2125.104 on
Arch Linux x86_64 and my CPU still spikes when using soundcloud or youtube.

[chro...@googlecode.com]

Comment #28 on issue 373489 by an...@euromake.com: GPU Process uses 70-100%

cpu when using google play music

https://code.google.com/p/chromium/issues/detail?id=373489

For me, updating to Chrome 39 triggered this issue. My Samsung Chromebook
is almost unusable now.

[chro...@googlecode.com]

Comment #29 on issue 373489 by nico...@gmail.com: GPU Process uses 70-100%

cpu when using google play music
https://code.google.com/p/chromium/issues/detail?id=373489

I'm able to reproduce this issue while using de Amazon Web Services console.
Chrome version: Version 39.0.2171.95 (64-bit)
OS: Arch Linux x86_64
Nvidia drivers version: 343.22-5

[chro...@googlecode.com]

Comment #31 on issue 373489 by alexhult...@gmail.com: GPU Process uses

70-100% cpu when using google play music

https://code.google.com/p/chromium/issues/detail?id=373489

The last couple of Chrome releases has been absolutely terrible for me. I
get 70 - 90% CPU usage in idle when not doing anything other than having my
Skype for Web open. It's the GPU Process burning its way through my desk.
My cursor stutters a lot.

I don't know if this is Microsoft doing some kind of "while(true)
doAlotOfShit();" or Chrome itself though.

[chro...@googlecode.com]

Comment #32 on issue 373489 by luke.hutch: GPU Process uses 70-100% cpu

when using google play music
https://code.google.com/p/chromium/issues/detail?id=373489

This appears fixed in the dev channel. See:
https://code.google.com/p/chromium/issues/detail?id=518209