1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking Benchmarking Platform
Phoromatic Test Orchestration

Video Acceleration Takes The Backseat On Chrome For Linux

Google

Published on 04 March 2014 09:41 AM EST
Written by Michael Larabel in Google
26 Comments

Due to notorious Linux graphics drivers, Google developers working on Chrome/Chromium aren't looking to enable hardware video acceleration by default anytime soon. The problem ultimately comes down to poor Linux graphics drivers.

A Phoronix reader tipped us off this morning about this code review on Chromium.org about moving the controlling of accelerated video decode support to the GPU blacklist. With the handling of video decode support being done from the GPU blacklist it would be easier and more streamlined to disable the blacklist and have easy access to VA-API video acceleration.

Back in 2012 I wrote about Google working on VA-API support in Chrome via VAVDA. Two years later, this code is still disabled by default. This Linux video acceleration support for Intel hardware and others isn't being enabled over concerns over bugs.

Ami Fischman explained in a bug comment yesterday, "There is a history of users disabling the blacklist (entirely) because they want a feature that is disabled. That destabilizes the entire browser, and users frequently forget about this action (and waste time trying to re-stabilize their browser later). If this landed I expect that sooner or later we'd get a rash of blog posts explaining how to get HW decode on linux 'for free' (by disabling the GPU blacklist) and the overall result for our Linux userbase would be a worse experience (because the blacklist will never be consulted on their system), not better (b/c they'll have HW acceleration of h.264 decode). This is a judgement call and I can certainly see how reasonable people can disagree, but this is my personal judgement."

Ami went on to imply that the VA-API Linux support will never be in good enough shape for Chrome, "We don't ship code we consider to be permanently 'experimental' or 'beta', only code we expect to be stable/production-quality eventually, if not at landing. This feature will never graduate to that status, so this CL is effectively shipping a feature that is known to be mostly-broken on most Linux installations."

Chrome developer Jorge Lucangeli Obes also commented on this report, "Supporting GPU features on Linux is a nightmare (I know from dealing with the GPU sandbox). Enabling this feature should come after thinking how we can make it available without making Chrome on Linux less stable."

There was then a proposal for introducing a GPU video decoding white-list to make it easier to mask systems with properly working VA-API support, but even that was shotdown due to varying graphics driver stacks, distributions, and hardware. The long story short is don't expect Google's Chrome/Chromium to have VA-API video acceleration support enabled by default anytime soon for Linux desktop users due to GPU driver concerns.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux News
  1. Linux Mint 17.2 Officially Released With Cinnamon/MATE Flavors
  2. Fedora For MIPS Is Now Out In Testing, Supports The Creator CI20
  3. KDE Plasma 5.3.2 Fixes Shutdown Scripts, Few Dozen Other Bugs
  4. KDE Marks Four Years In Its Process Of Porting To Wayland
  5. Btrfs In Linux 4.2 Brings Quota Updates, Many Fixes
  6. Latest Rumor Pegs Microsoft Wanting To Buy AMD
  7. The Next-Gen Phoronix Site Experience Is Almost Ready
  8. Exciting Features Merged So Far For The Linux 4.2 Kernel
  9. Mesa 10.6.1 Brings A Bug-Fix For Dota 2 Reborn
  10. DragonFlyBSD 4.2 Released: Brings Improved Graphics & New Compiler
Latest Articles & Reviews
  1. How KDE VDG Is Trying To Make Open-Source Software Beautiful
  2. Attempting To Try Out BCache On The Linux 4.1 Kernel
  3. CompuLab's Fitlet Is A Very Tiny, Fanless, Linux PC With AMD A10 Micro
  4. AMD A10-7870K Godavari: RadeonSI Gallium3D vs. Catalyst Linux Drivers
Most Viewed News This Week
  1. Kubuntu 15.10 Could Be The End Of The Road
  2. Linus Is Looking Forward To Merging KDBUS, But Not Convinced By Performance
  3. NVIDIA Starts Supplying Open-Source Hardware Reference Headers
  4. KDBUS Won't Be Pushed Until The Linux 4.3 Kernel
  5. Linux 4.2 Kernel Gets Port To New Processor Architecture
  6. The Staging Pull For Linux 4.2: "Big, Really Big"
  7. SteamOS "Brewmaster" Is Valve's New Debian 8.1 Based Version
  8. Jonathan Riddell Steps Down From The Kubuntu Council