1176457 - Graphics glitches appear everywhere in Graphene when run on Windows.

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Runtime, defect)

Description

[Brian R. Bondy [:bbondy]]

Attachment: d2d-rendering-problem.png

Please see the attached image of blizzard.com.

The problem seems to be with the azure D2D backend.

In this bug I'll just switch to the cairo backend so that Graphene is usable in Windows, I have a patch for this and will upload shortly.

pref("gfx.content.azure.backends", "cairo");

I'll also post another bug to investigate why the direct2d1.1 and direct2d backends do not work properly in Graphene.

Comment 1

[Brian R. Bondy [:bbondy]]

Attachment: cairo-rendering.png

Here's how the page renders (as normal) with cairo backend.

Note that toggling dom.ipc.tabs.disabled has no effect on the rendering for me either way.

Comment 2

[Paul Rouget [:paul]]

Do you have the same issue with the Firefox OS simulator?

Comment 3

[Brian R. Bondy [:bbondy]]

Note that this is on both a new Windows 8 Dell and also on a VM.
No I don't have the same problem with Firefox OS simulator.

Comment 4

[Brian R. Bondy [:bbondy]]

I think because of this, the simulator also uses cairo for rendering with azure:
https://dxr.mozilla.org/mozilla-central/source/b2g/components/OopCommandLine.js#33

Comment 5

[Paul Rouget [:paul]]

Can you disable tiling and keep direct2d see if that fixes the glitches?

Firefox Desktop uses d2d, right?

Comment 6

[Paul Rouget [:paul]]

(make sure to disable tiling in both the prefs and the settings)

Comment 7

[Brian R. Bondy [:bbondy]]

Firefox Desktop does yes.  I'll try the tiling thing.

Comment 8

[Brian R. Bondy [:bbondy]]

OK disabling tiling works on Windows so I'm going to go with that.

I verified as well and enabling tiling with D2D backend for azure also messes up in the same way on Desktop Firefox.  So I guess tiling + D2D isn't a supported config yet.  Uploading patch for review shortly.

Comment 9

[Brian R. Bondy [:bbondy]]

Attachment: Disable tiling

Comment 10

[Brian R. Bondy [:bbondy]]

Before landing I just wanted to check if it'd be better to set it in the b2g prefs under the same condition, since settings.js is modified I'm thinking that might be best.

Comment 11

[[:fabrice] Fabrice Desré]

(In reply to Brian R. Bondy [:bbondy] from comment #10)
> Before landing I just wanted to check if it'd be better to set it in the b2g
> prefs under the same condition, since settings.js is modified I'm thinking
> that might be best.

Yes, that looks like the right thing to do. thanks!

Comment 12

[Brian R. Bondy [:bbondy]]

I'm not sure if we're supposed to close out these larch only bugs or not. Please advise.

Turns out for windows it was already set to pref("layers.enable-tiles", false); for b2g/graphene. So it was only needed in the settings.js to fix the problem.  

Landed here:
http://hg.mozilla.org/projects/larch/rev/9ca8bc49bf32

Comment 13

[Kevin Grandon :kgrandon]

Landed in mozilla-central via bug 1204965.