Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31888 - [chromium] Rendering Artifacts on pages with HTML5 videos

Attached to Project: Arch Linux
Opened by Philip (PhilipWitte) - Wednesday, 10 October 2012, 21:36 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 24 October 2012, 10:56 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Chromium has horrible rendering artifacts on pages with HTML5 video players. It happens all the time when browsing Youtube, but isn't Youtube specific. The "articacts" are so bad, that it's impossible to use or often read other HTML widgets like comment boxes. It's very annoying because I can't leave comments on some videos.

On pages with HTML5 videos, the fixed HTML element stay in place, and other elements only render in "tiles". When an animated element updates, often only half of it actually renders while the "tile" next to is remains visually unchanged.

This may be directly related to my setup in some way:

AMD Phenom II x4 920
ATi Radeon HD 4870 using the Catalyst drivers from the offical HD234k repo and Xorg 1.1.1
GnomeShell 3.4.2 with "export CLUTTER_VBLANK=none" set in /etc/profile

This bug has been happening for now, and I'm not sure when it started. However, it didn't happen when I had Chrome and Ubuntu 12.04 installed.

Screenshot: http://reign-studios.com/ChromiumBug/screenshot.jpg

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 24 October 2012, 10:56 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Probably an upstream and/or graphics card driver issue that occurs when hardware accelerated compositing is enabled. Please report upstream if it persists.
Comment by Evangelos Foutras (foutrelis) - Thursday, 11 October 2012, 15:56 GMT
Set CHROMIUM_FLAGS="--disable-accelerated-compositing" in /etc/chromium/default.

This is obviously a workaround, so you can try finding report(s) about this issue on Chromium's issue tracker [1].

Can't realistically do anything on Arch's side to fix this kind of problems.

[1] http://code.google.com/p/chromium/issues/list
Comment by Philip (PhilipWitte) - Friday, 12 October 2012, 03:52 GMT
Awesome, that fixed the problem, thanks a lot.

I wasn't sure if this was a bug with upstream Chromium or an Arch specific build, so I reported it here. Thanks for the clarification.

Loading...