Closed Bug 1309071 Opened 9 years ago Closed 9 years ago

Enabling E10S on Fennec Aurora completely breaks rendering, can't even display about:config to disable it

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Version:
51 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: mozilla.org, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Build ID: 20160920074044 Steps to reproduce: Latest Aurora nightly on Android Marshmallow. Create a new browser.tabs.remote.autostart=true preference in about:config. Restart the browser and attempt to navigate to any page. Actual results: Tapping on a link does nothing. Opening a link in a new tab loads an empty tab, sometimes with the bottom third of the tab black. Expected results: Rendering should work more or less the same as if E10S were disabled.
Tested on latest Aurora on a Sony Xperia Z5 Premium (Android 6.0.1). I've tried with "browser.tabs.remote.autostart" set to true, also with "browser.tabs.remote.force-enabed" set to true; I wasn't able to reproduce this issue. Can you please provide more info as: the device you are using, can you record the issue, or provide the logcat. Thanks.
Flags: needinfo?(mozilla.org)
Is browser.tabs.remote.autostart valid for Firefox for Android? Last I knew the preference did not function.
Flags: needinfo?(blassey.bugs)
Flags: needinfo?(blassey.bugs) → needinfo?(snorp)
e10s is not supported in Fennec. We added support for the pref for development purposes only.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(snorp)
Resolution: --- → INVALID
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.