Bug#1050677: RE: chromium: VAAPI acceleration not working on Chromium 116

Leandro Cunha Sun, 25 Feb 2024 13:21:14 -0800

Hi,

On Sun, Feb 25, 2024 at 5:59 PM Andres Salomon <dilin...@queued.net> wrote:
>
> Hi,
>
> Can you please verify that this has been fixed since Chromium >= 118? We
> currently have Chromium 122 in unstable/testing/stable.
>
> Thanks,
> Andres
>
> On Wed, 27 Sep 2023 00:55:04 -0300 Leandro Cunha
> <leandrocunha...@gmail.com> wrote:
> > Hi,
> >
> > It's a problem that persists in 117 on unstable, although on the
> > Chrome unstable channel (version 118.x) it seems to be resolved.
> >
> > Graphics Feature Status
> > =======================
> > *   Canvas: Hardware accelerated
> > *   Canvas out-of-process rasterization: Disabled
> > *   Direct Rendering Display Compositor: Disabled
> > *   Compositing: Hardware accelerated
> > *   Multiple Raster Threads: Enabled
> > *   OpenGL: Enabled
> > *   Rasterization: Hardware accelerated
> > *   Raw Draw: Disabled
> > *   Skia Graphite: Disabled
> > *   Video Decode: Software only. Hardware acceleration disabled
> > *   Video Encode: Software only. Hardware acceleration disabled
> > *   Vulkan: Enabled
> > *   WebGL: Hardware accelerated
> > *   WebGL2: Hardware accelerated
> > *   WebGPU: Disabled
> >
> > Driver Bug Workarounds
> > ======================
> > *   adjust_src_dst_region_for_blitframebuffer
> > *   clear_uniforms_before_first_program_use
> > *   count_all_in_varyings_packing
> > *   disable_post_sub_buffers_for_onscreen_surfaces
> > *   enable_webgl_timer_query_extensions
> > *   exit_on_context_lost
> > *   msaa_is_slow
> > *   rely_on_implicit_sync_for_swap_buffers
> > *   disabled_extension_GL_KHR_blend_equation_advanced
> > *   disabled_extension_GL_KHR_blend_equation_advanced_coherent
> > *   disabled_extension_GL_MESA_framebuffer_flip_y
> >
> > Problems Detected
> > =================
> > *   WebGPU has been disabled via blocklist or the command line.
> >     Disabled Features: webgpu
> >
> > *   Accelerated video encode has been disabled, either via blocklist,
> > about:flags or the command line.
> >     Disabled Features: video_encode
> >
> > *   Accelerated video decode has been disabled, either via blocklist,
> > about:flags or the command line.
> >     Disabled Features: video_decode
> >
> > *   Clear uniforms before first program use on all platforms:
> >     (http://crbug.com/124764), (http://crbug.com/349137)
> >     Applied Workarounds: clear_uniforms_before_first_program_use
> >
> > *   Mesa drivers in Linux handle varyings without static use incorrectly:
> >     (http://crbug.com/333885)
> >     Applied Workarounds: count_all_in_varyings_packing
> >
> > *   On Intel GPUs MSAA performance is not acceptable for GPU rasterization:
> >     (http://crbug.com/527565), (http://crbug.com/1298585)


This issue has been solved!

I tested a website here that needed it and it opened normally. I'm
going to close the bug, if anyone finds a problem they can reopen it
and remove it from the debbugs arquive
(https://en.wikipedia.org/wiki/Debbugs).

*   Canvas: Hardware accelerated
*   Canvas out-of-process rasterization: Disabled
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Hardware accelerated
*   Multiple Raster Threads: Enabled
*   OpenGL: Enabled
*   Rasterization: Hardware accelerated on all pages
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   Video Decode: Hardware accelerated
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Disabled
*   WebGL: Hardware accelerated
*   WebGL2: Hardware accelerated
*   WebGPU: Disabled

-- 
Cheers,
Leandro Cunha

Bug#1050677: RE: chromium: VAAPI acceleration not working on Chromium 116

Reply via email to