Bug 12407

Summary: Bitmap glitches in gecko browsers with xorg-server-1.4
Product: xorg Reporter: Lukasz Krotowski <lukasz.krotowski>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED WORKSFORME QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Google example.
none
Phoronix example.
none
Xorg log.
none
Xorg config.
none
Testcase. none

Description Lukasz Krotowski 2007-09-12 10:35:19 UTC
After updating xorg-server-1.3.0.0 to xorg-server-1.4 bitmap glitches appeared in gecko-based browsers (seamonkey, kazehakase) -- screenshots attached.
Comment 1 Lukasz Krotowski 2007-09-12 10:38:59 UTC
Created attachment 11530 [details]
Google example.
Comment 2 Lukasz Krotowski 2007-09-12 10:40:39 UTC
Created attachment 11531 [details]
Phoronix example.
Comment 3 Michel Dänzer 2007-09-13 09:43:36 UTC
Please attach the full config and log files.
Comment 4 Lukasz Krotowski 2007-09-13 10:16:54 UTC
Created attachment 11541 [details]
Xorg log.

Naturally, here's full log (sorry it's so late, it's because of I-must-have-AMD-specs freedesktop.org downtime ;) ).
Comment 5 Lukasz Krotowski 2007-09-13 10:20:01 UTC
Created attachment 11542 [details]
Xorg config.
Comment 6 Lukasz Krotowski 2007-09-13 10:21:40 UTC
Created attachment 11543 [details]
Testcase.

Simple testcase. It seems that only background images are broken.
Comment 7 Michel Dänzer 2007-09-13 10:25:34 UTC
Does it also happen without Option "MigrationHeuristic" or "AccelMethod"?
Comment 9 Lukasz Krotowski 2007-09-13 10:47:43 UTC
Well, using either XAA or not using greedy MigrationHeuristic fixes bitmaps. What's more important EXA doesn't hang hard without greedy MigrationHeuristic (that's something new ;) ) on my machine.

/me blushes for not trying that. ;)

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.