Open Bug 599962 Opened 10 years ago Updated 10 years ago
Chrome Experiments : Blob has drawing artifacts
139.29 KB, image/png
214.78 KB, image/png
136.88 KB, image/png
200.32 KB, image/png
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:2.0b7pre) Gecko/20100927 Firefox/4.0b7pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:2.0b7pre) Gecko/20100927 Firefox/4.0b7pre Drawing artifacts are visible at the top of the window in which Blob is launched. Reproducible: Always Steps to Reproduce: 1. Launch Chrome Experiment : Blob 2. Notice **** near the top of the screen (same colour as the blob). 3. Artifacts at the top of the screen disappear if the blob comes too close, or makes contact with them. Disappears and does not return. Actual Results: Looks like part of the blob got stuck at the top of the screen upon start up. Experiment looks and works fine, otherwise. Expected Results: This experiment should run exactly as it does, without the artifact popping up in the beginning. I have attached a screen shot of what I was seeing.
I don't see this on Mac, so maybe related to HA? Crystal, what happens if you turn off D2D?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: chromeexperiments → [chromeexperiments]
I also don't have any problem on linux/GL. To disable D2D as David suggests, go to about:config and search for direct2d If that still doesn't work, try setting layers.accelerate-none=true (disables D3D compositing).
WFM: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7pre) Gecko/20100927 Firefox/4.0b7pre works with or without HA on
Personally I cannot reproduce this on Windows with any permutation of D3D9Layers/D2D settings.
(In reply to comment #2) > I don't see this on Mac, so maybe related to HA? Crystal, what happens if you > turn off D2D? Turned off D2D, I got the exact same thing. Still have artifacts at the top.
Can you please then try turning off accelerated layers as explained in comment 3 ?
gfx.direct2d.disabled=true gfx.direct2d.force-enabled=true layers.accelerate-none=true
(In reply to comment #8) > gfx.direct2d.disabled=true > gfx.direct2d.force-enabled=true I think this one is wrong? Don't want to force-enable here as well as disable, I suspect.
(In reply to comment #9) > (In reply to comment #8) > > gfx.direct2d.disabled=true > > gfx.direct2d.force-enabled=true > > I think this one is wrong? Don't want to force-enable here as well as disable, > I suspect. Indeed, so we still don't know about D2D until without force-enabled. Likewise, layers.accelerate-none=true is good but make sure you don't have layers.accelerate-all=true !
In both cases accelerate-none and disabled overrule any enabling settings. So this was without any acceleration. But the best way to verify is the about:support graphics section!
set gfx.direct2d.force-enabled to false. layers.accelerate-all was =true, so I also set that to false this time. the following attachment will be a screen of about:support graphics, after I fixed the preferences, restarted minefield and ran the blob exp. also, included screens of about:config so you know which prefs I set. Hope I got it right this time.
Screen shots of preferences and about:support graphics. Goes with the blob artifacts pic in my last comment.
OK, thanks, this time you really disabled D2D and D3D, the problem persists. So this is really a Canvas rendering bug. CCing a couple of people...
You need to log in before you can comment on or make changes to this bug.