“Override Software Rendering List” and “GPU Compositing On All Pages” – New In About:Flags

Hi Guys, a quick post to let you all know about two new things added to about:flags page in Chromium. Both of them related to GPU-acceleration.

Override software rendering list
Overrides the built-in software rendering list and enables GPU-acceleration on unsupported system configurations.

GPU compositing on all pages
Uses GPU accelerated compositing on all pages, not just those that include GPU-accelerated layers.

Anyone with more info on this ?

In Category: Google Chrome


Dinsan made Google Chrome his default browser within hours of its release. He fell in love with Chromebooks from the day he first touched one and is currently obsessed with Chromecasts.

Show 6 Comments
  • ka_ko 20/05/2011, 3:57 am

    well, those 2 new flags are the first GPU acceleration related flags that appear in the Mac OSX version of chrome.

    • Dinu 20/05/2011, 4:04 am

      cool ! thanks for the info !

  • James 20/05/2011, 9:28 pm

    The override one is for getting WebGL on XP, I think.

    • Henry Young 21/05/2011, 4:48 am

      It is also used for Macs with ATI GPU’s and some ATI and NVIDIA GPU’s in Windows, OS X and Linux.

      • James 21/05/2011, 8:37 pm

        I have NVIDIA, so that might be why WebGL doesn’t work for me (unless I use the command line switch).

  • MaddyY 25/10/2012, 4:47 pm

    I’m using GNU/Linux, and when I enable both those flags on Chromium (23.0.1271.1 (Developer Build 157674) Kubuntu 12.10), pages with a lot of active content seem to become much slower (especially when scrolling). I’m currently using my integrated GPU (Intel’s HD 3000 or whatever it’s called). Even resizing this comment box slowed the browser down to (from just looking at it) about 10 FPS.

    Does anyone know if this is caused by enabling these two options? I keep hearing they cause a performance INCREASE but I want to make sure it’s actually working.

    BTW I get the error “ERROR:gles2_cmd_decoder.cc(5176)] : RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering or is not ‘texture complete'” as one of the errors repeated a lot in “about:gpu-internals”.