All users were logged out of Bugzilla on October 13th, 2018

e10s - No rendering of Firefox window with skia enabled in prefs.js

NEW
Unassigned

Status

()

4 years ago
3 years ago

People

(Reporter: pascalc, Unassigned)

Tracking

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(e10s-)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8521754 [details]
skia-e10s-bug.png

Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0

1/ Have a prefs.js file with skia backend activated:

user_pref("gfx.content.azure.backends", "skia");

2/ launch Nightly.

Expected result:
Firefox launches with a UI

Actual result:
No rendering of chrome or content area (see screenshot)

If you remove the user_pref("gfx.content.azure.backends", "skia"); line, things are back to normal

Comment 1

4 years ago
Can you post your about:support graphics section?
Component: General → Graphics
Product: Firefox → Core
Version: unspecified → Trunk
I imagine this is a duplicate of bug 1009722 (bug 996611.)
(Reporter)

Comment 3

4 years ago
(In reply to :Gijs Kruitbosch from comment #1)
> Can you post your about:support graphics section?

Description de la carte	Intel Open Source Technology Center -- Mesa DRI Intel(R) Ivybridge Mobile
Fenêtres avec accélération graphique	0/1 Basic
ID du périphérique	Mesa DRI Intel(R) Ivybridge Mobile
ID du vendeur	Intel Open Source Technology Center
Rendu WebGL	Intel Open Source Technology Center -- Mesa DRI Intel(R) Ivybridge Mobile
Version du pilote	3.0 Mesa 10.3.0
windowLayerManagerRemote	false
AzureCanvasBackend	skia
AzureContentBackend	skia
AzureFallbackCanvasBackend	none
AzureSkiaAccelerated	0
tracking-e10s: --- → +
I was under the impression that skia worked with e10s disabled when I tracked this. Milan just informed me that that is not the case, so I'm -'ing this.
tracking-e10s: + → -
You need to log in before you can comment on or make changes to this bug.