- I agree. The only reason I decided not to do it was because there is an AUR package so it seems that there are some people interested in it. But then again; if there are enough users, they can make a separate wiki page. Lonaowna (talk) 11:07, 27 February 2014 (UTC)
Hi. I would like to mention here that I've had tearing issues with chromium (probably affects Chrome too) which were easily visible in youtube videos (with html5 player, I haven't tried using flash player) while using radeon ati(the open source driver, not fglrx); but tearing was also somewhat visible when scrolling. It's as if VSync was off but only for chromium, however everywhere else (in X ie. moving windows, vlc, parole media player) VSync was on and working perfectly.
The solution to this was typing chrome://flags (typing that in chromium address bar) and click Enable on this one:
Override software rendering list (which is at the top of the list of flags on that page), so it looks like this after Enabling:
" Override software rendering list Mac, Windows, Linux, Chrome OS, Android
Overrides the built-in software rendering list and enables GPU-acceleration on unsupported system configurations. #ignore-gpu-blacklist
Apparently whatever this did it made it look like Chromium has VSync on and no tearing takes place anymore especially in html5 youtube videos. Enabling the FPS counter further showed me that the fps doesn't go beyond 60fps, usually around 33fps for me while playing html5 youtube videos with a chromium addon.
I used this simple video to test if tearing was gone: https://www.youtube.com/watch?v=laDA1NOn-C4
- As mentioned in Chromium#Force_3D_acceleration_in_Flash_Player_and_the_browser, "override software rendering list" can cause unstable behaviour, even crashing the host. I've added a notice, but issues should be mentioned upstream against the bug reports mentioned in
chrome://gpuif appropriate. Your best bet is to install AUR from the AUR. Closing. --Alad (talk) 05:29, 15 July 2014 (UTC)