| Summary: | Chromium Stable 57 breaks hw-accelerated mp4/avc video playback (with Gallium/Mesa support) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | batbajar gombo <mageia> |
| Component: | RPM Packages | Assignee: | Christiaan Welvaart <cjw> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | marja11 |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | chromium-browser-stable-57.0.2987.133-1.mga5.i586.src.rpm | CVE: | |
| Status comment: | |||
|
Description
batbajar gombo
2017-04-29 11:03:23 CEST
Assigning to the registered maintainer Assignee:
bugsquad =>
cjw Could you try with chromium-browser-stable-58.0.3029.110-0.1.mga5 in updates_testing? I didn't change anything but the 3D acceleration is reported OK for this version. I tried to test on the same graphics hardware but it appears that mainboard is in my server where I don't usually run an X server, so I only have older and newer AMD hardware to test on. (01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200]; CPU is a dual core Athlon II X2 250e). (In reply to Christiaan Welvaart from comment #2) > Could you try with chromium-browser-stable-58.0.3029.110-0.1.mga5 in > updates_testing? I didn't change anything but the 3D acceleration is > reported OK for this version. > > I tried to test on the same graphics hardware but it appears that mainboard > is in my server where I don't usually run an X server, so I only have older > and newer AMD hardware to test on. (01:05.0 VGA compatible controller: > Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200]; CPU is a dual > core Athlon II X2 250e). I did try chromium-browser-stable-58.0.3029.110-0.1.mga5 from updates_testing today. Unfortunately, it shows exactly the same symptoms. Fact is, something changed from 55 upwards(maybe upstream!) and broke hw-accelerated video rendering with MESA/Gallium support. I think the missing GL_*DATA* is the clue. If you need me to provide anything else from my system, or do some more testing, please let me know. Here is the output of chrome://gpu. Not much difference to v57. ## chrome://gpu @ 58.0.3029.110-0.1.mga5 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: Disabled 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 WebGL2: Hardware accelerated Driver Bug Workarounds adjust_src_dst_region_for_blitframebuffer clear_uniforms_before_first_program_use count_all_in_varyings_packing decode_encode_srgb_for_generatemipmap disable_framebuffer_cmaa disable_texture_storage dont_remove_invariant_for_fragment_input force_cube_map_positive_x_allocation init_texture_max_anisotropy regenerate_struct_names remove_invariant_and_centroid_for_essl3 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 Linux AMD drivers incorrectly return initial value of 1 for TEXTURE_MAX_ANISOTROPY: 348237 Applied Workarounds: init_texture_max_anisotropy Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args Linux AMD drivers handle struct scopes incorrectly: 403957 Applied Workarounds: regenerate_struct_names Linux ATI drivers crash on binding incomplete cube map texture to FBO: 518889 Applied Workarounds: force_cube_map_positive_x_allocation Linux Mesa drivers crash on glTexSubImage2D() to texture storage bound to FBO: 521904 Applied Workarounds: disable_texture_storage Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198 Applied Workarounds: disable_framebuffer_cmaa adjust src/dst region if blitting pixels outside read framebuffer on Linux AMD: 664740 Applied Workarounds: adjust_src_dst_region_for_blitframebuffer AMD drivers in Linux require invariant qualifier to match between vertex and fragment shaders: 659326, 639760 Applied Workarounds: dont_remove_invariant_for_fragment_input, remove_invariant_and_centroid_for_essl3 Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Decode and Encode before generateMipmap for srgb format textures on Linux AMD: 634519 Applied Workarounds: decode_encode_srgb_for_generatemipmap Accelerated rasterization has been disabled, either via blacklist, about:flags or the command line. Disabled Features: rasterization Raster is using a single thread. Disabled Features: multiple_raster_threads Native GpuMemoryBuffers have been disabled, either via about:flags or command line. Disabled Features: native_gpu_memory_buffers Version Information Data exported 7.6.2017 11:23:26 Chrome version Chrome/58.0.3029.110 Operating system Linux 4.4.68-server-1.mga5 Software rendering list version 0 Driver bug list version 9.36 ANGLE commit id unknown hash 2D graphics backend Skia/58 4c81ba6ba3a3270db809bf7d4c3bc782694a56a4 Command Line Args --ppapi-flash-path=/opt/google/chrome/PepperFlash/libpepflashplayer.so --ppapi-flash-version=25.0.0.148 --flag-switches-begin --ignore-gpu-blacklist --flag-switches-end Driver Information Initialization time 200 In-process GPU false Passthrough Command Decoder false Sandboxed false GPU0 VENDOR = 0x1002, DEVICE= 0x9610 Optimus false Optimus false AMD switchable false Driver vendor Mesa Driver version 10.5.9 Driver date Pixel shader version Vertex shader version Max. MSAA samples 0 Machine model name Machine model version GL_VENDOR GL_RENDERER GL_VERSION GL_EXTENSIONS Disabled Extensions GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent Window system binding vendor SGI Window system binding version 1.4 Window system binding extensions GLX_ARB_create_context GLX_ARB_create_context_profile GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_multisample GLX_EXT_create_context_es2_profile GLX_EXT_framebuffer_sRGB GLX_EXT_import_context GLX_EXT_texture_from_pixmap GLX_EXT_visual_info GLX_EXT_visual_rating GLX_MESA_copy_sub_buffer GLX_OML_swap_method GLX_SGI_swap_control GLX_SGIS_multisample GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_SGIX_visual_select_group GLX_INTEL_swap_event Window manager KWin XDG_CURRENT_DESKTOP KDE Compositing manager Yes Direct rendering Yes Reset notification strategy 0x0000 GPU process crash count 0 System visual ID 33 RGBA visual ID 120 Compositor Information Tile Update Mode One-copy Partial Raster Enabled GpuMemoryBuffers Status ATC Software only ATCIA Software only DXT1 Software only DXT5 Software only ETC1 Software only R_8 Software only RG_88 Software only BGR_565 Software only RGBA_4444 Software only RGBX_8888 Software only RGBA_8888 Software only BGRX_8888 Software only BGRA_8888 Software only YVU_420 Software only YUV_420_BIPLANAR Software only UYVY_422 Software only Log Messages [4931:4931:0607/112310.902626:ERROR:sandbox_linux.cc(343)] : InitializeSandbox() called with multiple threads in process gpu-process. ## I also made a color-coded diff (output of chrome://gpu) for v55 versus v57. You can see the result here:: https://ibb.co/jeeGav Besides the missing GL_* info, there are 4 more "Driver Bug Workarounds" applied, a new "Graphics Fearure" added ("WebGL2") and 2 "Disabled Extensions". Any thoughts? Thanks. Regards, B.Gombo Please test with chromium 60 - I disabled my "build with system mesa" experiment which may have caused the problems you see. (In reply to Christiaan Welvaart from comment #5) > Please test with chromium 60 - I disabled my "build with system mesa" > experiment which may have caused the problems you see. This appears to have solved the issue entirely. No more dropped frames!! ;-) Cheers! Fixed according to previous comment. Thanks for testing! Resolution:
(none) =>
FIXED |