Bug 79529 - black areas when running chromium own build
Summary: black areas when running chromium own build
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-02 07:45 UTC by Arkadiusz Miskiewicz
Modified: 2014-06-06 11:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
screenshot of black taskbar areas (216.46 KB, image/jpeg)
2014-06-02 07:45 UTC, Arkadiusz Miskiewicz
no flags Details
dmesg (109.42 KB, text/plain)
2014-06-02 07:45 UTC, Arkadiusz Miskiewicz
no flags Details
xorg log (24.85 KB, text/plain)
2014-06-02 07:45 UTC, Arkadiusz Miskiewicz
no flags Details

Description Arkadiusz Miskiewicz 2014-06-02 07:45:10 UTC
Created attachment 100270 [details]
screenshot of black taskbar areas

Dell XPS 15 (Haswell) one (00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]))

KDE 4.11.4

chromium-browser (35.0.1916.114, own build available at http://carme.pld-linux.org/~glen/th/x86_64/)

intel git driver (ffbe0aa1851c35cc2403633ca493e9fc6a471fd4)

kernel 3.15.0-rc7-00118-ga4bf79e

mesa 10.2rc5

When running that chromium browser the screen redraws in weird (slow) way initially and then kde task bar becomes black partially. Moving over mouse on it sometimes cures it.
Comment 1 Arkadiusz Miskiewicz 2014-06-02 07:45:34 UTC
Created attachment 100271 [details]
dmesg
Comment 2 Arkadiusz Miskiewicz 2014-06-02 07:45:56 UTC
Created attachment 100272 [details]
xorg log
Comment 3 Arkadiusz Miskiewicz 2014-06-02 07:55:39 UTC
One additional note - running official google chrome binaries doesn't cause this effect. I'm able to trigger these black areas only when using this chromium build. I wasn't able to find any other program that would cause similar problem as chromium causes but still looking...
Comment 4 Arkadiusz Miskiewicz 2014-06-02 10:51:46 UTC
How to reproduce. Run google-chrome, open some page and THEN run chromium browser. Black areas should appear on the same desktop chromium was run.

It looks like chromium is conflicting with google chrome somehow (maybe chromium tries to use google chrome rendering processes or something similar).

Anyway even if that true then that shouldn't affect rendering outside of chromium window:
< ickle> touching areas outside of the app is b0rked

- tested few driver versions as old as 2.99.904 - no change
- i915.enable_fbc=0 i915.enable_rc6=0 i915.enable_psr=0 - also no change
- few renering settings in "desktop effects"; xrender was producing even worse results (strips + black areas; black areas with strips etc); found no good working configuration
Comment 5 Chris Wilson 2014-06-03 13:13:32 UTC
Fwiw, can you disable hw acceleration using chrome://settings/ I am not sure how that interacts with chrome://flags/ but the checkbox in //settings/ seems to do what I want.
Comment 6 Chris Wilson 2014-06-05 12:36:52 UTC
Definitely curious what happens with the various Cr render backends.
Comment 7 Jay Little 2014-06-05 12:54:18 UTC
For what it's worth, I was having Chromium rendering issues with the latest driver but it appears that the patch for this bug might've resolved those issues:

https://bugs.freedesktop.org/show_bug.cgi?id=79517

Might be worth having Arkadiusz try that patch and see if it fixes his Chromium issues.
Comment 8 Chris Wilson 2014-06-05 13:00:48 UTC
I've pushed that patch (right behind a very, very scary patch)...
Comment 9 Jay Little 2014-06-05 13:12:14 UTC
That does look scary.  Screw it.  I'll give it a go.
Comment 10 Arkadiusz Miskiewicz 2014-06-05 13:23:15 UTC
Too early to tell for sure but so far I was unable to reproduce black areas chromium a problem with current git (9566fc0ccc71bc4fcd6bf83b567a41cc5366f5ee). Also using xrender render backend does not cause problems.

Will do more testing to be sure that problem is gone.
Comment 11 Chris Wilson 2014-06-06 11:38:30 UTC
Tempting fate.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.