612932 - [D2D] Visual crud/gunk in Google Reader list view using Firefox 4 (pre8) - regression from Firefox 3.6.x

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect)

Description

[Adrian Sampaleanu]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.589.0 Safari/534.13
Build Identifier: http://hg.mozilla.org/mozilla-central/rev/4c960203c759

Some item summaries in the list view of Google Reader show a pixel thick row of junk below the summary.

Reproducible: Always

Steps to Reproduce:
1. Add the Playstation blog at http://feeds.feedburner.com/PSBlog to Google Reader
2. View the feed in list view (not expanded).

Actual Results:  
Notice that some entries have some pixel junk below the entry text. 

Some entries that exhibit this problem:
Nov. 17 2010 - VUDU Comes to the PS3, Adding Another Choice for PSN Members to Experience Media Instantly
Nov. 15 2010 - ModNation Monday: Carnival Parts Pack and “Free” Progressive Kart next week!
Nov. 10 2010 - This Week in PlayStation Home: 1.4 Client Update details, LittleBigPlanet, and More!
Nov. 3 2010 - PlayStation Move: 1 Million Units Shipped in North America, a Growing Library of Titles


Expected Results:  
Feed title in list view should have no junk/gunk/crud showing.

I believe that older (more than 2 months?) versions of Firefox 4 didn't exhibit this problem.
The junk is evident when the page is rendered at 100% - at other magnifications it seems to go away.

Firefox 3.6.x running on Windows Vista SP2 32 bit, does not have this problem.

Comment 1

[Adrian Sampaleanu]

Attachment: Screenshot showing junk in Google Reader list view.

Comment 2

[Adrian Sampaleanu]

Chromium nightly doesn't exhibit the problem.

Comment 3

[(mostly gone) XtC4UaLL [:xtc4uall]]

Adrian, does the Issue still happen with a recent Nightly Build?
-> http://nightly.mozilla.org/

Comment 4

[Adrian Sampaleanu]

Yes, with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101205 Firefox/4.0b8pre ID:20101205074420 it's still happening. 

The blog (PSBlog) I mentioned above shows the problem for the entry:

Nov. 28, 2010 - The Drop: Week of Nov 29th 2010 New Releases

This blog, Cloud Computing with Zero Deployment (http://gridgaintech.wordpress.com/feed/) show the problem with the entry:

Nov. 22, 2010 - GridGain + Scala at NYC JavaSIG, November 23


Really, the problem happens often enough that it shouldn't be very hard to find.

Comment 5

[Adrian Sampaleanu]

I just checked with the very latest tinderbox build since I thought the latest nightly might've been newer than the tinderbox build I had reported on in the previous comment. With Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101205 Firefox/4.0b8pre ID:20101206025655 the problem still exists.

Comment 6

[(mostly gone) XtC4UaLL [:xtc4uall]]

What happens if you disable Hardware Acceleration in Tools/Options/Advanced/General and Restart Fx?
What happens if you only set "layers.accelerate-none" to "true" in about:config?
What's your Graphics Info from about:support (Bottom)?

Comment 7

[Adrian Sampaleanu]

The artifacts are there with acceleration disabled, too. layers.accelerate-none is set to true when you disable acceleration in the options UI, so I'm not sure what you mean by trying having "only" this set.

I had set some of the acceleration properties myself based on some older blog postings before a UI was exposed for it and maybe I'm missing or have some extra settings. 

I remember having one setting that referred to layers.*.d3d10 (something like that). When I was looking at the setting now, it was black indicating that it was changed from the default. I reset it and the value disappeared (it used to be a boolean and once reset it changed to string). Upon restarting, that setting completely disappeared. Is that still required for completely accelerating all features?

With acceleration turned on, I have these settings:

layers.accelerate-all;true
layers.accelerate-none;false
layers.prefer-d3d9;false
layers.prefer-opengl;false

Shouldn't one of the .prefer settings be set to true?  What is the definitive set of options and what should it be set to when accelerations is on? Is it the above four settings?


The graphics section of my about:support is:
Adapter Description: ATI Radeon HD 5700 Series
Vendor: ID1002
Device: ID68b8
Adapter RAM: 1024
Adapter Drivers: aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Driver Version: 8.791.0.0
Driver Date:
Direct2D Enabled: true
DirectWrite Enabled: true
GPU Accelerated Windows: 3/3 Direct3D 10

Comment 8

[Adrian Sampaleanu]

I can confirm that the problem appears on brand new Minefield installation running on on a system with NVidia graphics. Furthermore, I noticed that while the problem manifests itself on some reader entries while viewing at 100%, changing the magnification, say to 120%, makes the problem shift to other entries while disappearing from those entries that were showing the artifacts at 100%.

Comment 9

[Bobby Johnson [:rjohnson19]]

I see this with hardware acceleration on. With it off ("Use hardware acceleration when available" unchecked), the problem doesn't seem to occur for me.
This is with default zoom level, viewing a single feed's list view.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b10pre) Gecko/20110116 Firefox/4.0b10pre

Adapter Description: ATI Mobility Radeon HD 3650
Vendor ID: 1002
Device ID: 9591
Adapter RAM: 1024
Adapter Drivers:atiumd64 atidxx64 atiumdag atidxx32 atiumdva atiumd6a atitmm64
Driver Version: 8.632.1.2000
Driver Date: 8-17-2009
Direct2D Enabled: true
DirectWrite Enabled: true (6.1.7600.20781)
WebGL Renderer: TransGaming Inc. -- ANGLE -- OpenGL ES 2.0 (git-devel Jan 16 2011 04:05:41)
GPU Accelerated Windows: 1/1 Direct3D 10

Comment 10

[Bobby Johnson [:rjohnson19]]

I just found one list entry where I see the issue with hardware acceleration off, so confirmed with hardware acceleration both on and off.

Comment 12

[Rey Bango]

@Bobby: Retested the issue I reported in Bug 626241. Turning hardware acceleration off *does* resolve the issue. The reason it didn't seem to before was because I didn't close/restart Fx 4.0b9. It appears that I needed to do that for hardware acceleration to be truly disabled. When disabled, the rendering artifacts do not appear.

Apologies for the confusion. Perhaps the hardware acceleration option should get a dialog prompting for a restart.

Comment 14

[(mostly gone) XtC4UaLL [:xtc4uall]]

Wondering if this Difference in Rendering is expected due to D2D/DW?
Does Google set wrong Expectations in the Code as in other similar Cases?

Comment 15

[Rey Bango]

Note that this still is happening in final and I had to set gfx.direct2d.disabled = true to fix. Turning off hardware acceleration via the options dialog had no effect.

Comment 16

[Alice0775 White]

Attachment: This also happens on IE9(Enabled GPU) Windows7 SP1 x64

I guess this is Google's CSS problem.

Comment 18

[Matthias Versen [:Matti]]

Is this still an issue ?

Comment 19

[Adrian Sampaleanu]

I haven't seen this in quite a while. In any case, Google Reader is being retired this July.

Comment 20

[Adrian Sampaleanu]

I haven't seen this in quite a while. In any case, Google Reader is being retired this July. You can mark this resolved on my account.

Comment 21

[Matthias Versen [:Matti]]

thank you for the response, marking wfm