<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 9/17/14 12:19 PM, Paul Rouget wrote:<br>
</div>
<blockquote cite="mid:20140917171931.GK12820@x240" type="cite">
<pre wrap="">This is a larger issue than just the devtools.
Can we make sure the fx-team folks know about this?
Brian Grinstead wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Just a heads up, now that e10s is being prompted to be turned on for
Nightly users, some people are getting bit with a problem if they
share profiles with a stable release. Here is an example:
<a class="moz-txt-link-freetext" href="https://twitter.com/bittersweetryan/status/512279927660359680">https://twitter.com/bittersweetryan/status/512279927660359680</a>.
What happens is that it turns on the e10s prefs for their profile
for Nightly (35), then when they open stable (32) the tools are
completely broken and won't even open. The solution is to have them
manually set the browser.tabs.remote and
browser.tabs.remote.autostart prefs to false or to uncheck the e10s
box in the preferences page in Nightly.
Unfortunately, the same issue happens in Beta (33) so this will be a
problem for the next release cycle as well unless if a change was
made to DevTools in beta or if the prompt to turn on e10s somehow
only targeted the nightly update channel. I haven't looked into
what the fix would be, and I'm not sure if this is such an edge case
that we should ignore it or if we should do something about it.
Things begin to work again in Aurora (34).
Brian
_______________________________________________
dev-developer-tools mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dev-developer-tools@lists.mozilla.org">dev-developer-tools@lists.mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://lists.mozilla.org/listinfo/dev-developer-tools">https://lists.mozilla.org/listinfo/dev-developer-tools</a>
</pre>
</blockquote>
<pre wrap="">-- Paul
</pre>
</blockquote>
Cross posting to firefox-dev, since this seems like an issue broader
than devtools. What is happening is that a user enabled e10s (most
likely from the Nightly prompt), then later opened stable with the
same profile. At this point devtools won't open at all due to some
errors when running the tools with e10s in 32 and 33.<br>
<br>
I'm assuming that there may be similar issues in other parts of the
browser - would it make sense for enabling e10s via the Nightly
prompt to only apply to the Nightly channel?<br>
<br>
Brian<br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</body>
</html>