<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, May 25, 2014 at 12:20 AM, Jayakumar Sadhasivam <span dir="ltr"><<a href="mailto:iamjayakumars@gmail.com" target="_blank">iamjayakumars@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:verdana,sans-serif">I think issue only with WINDOWS Firefox Nightly. <br></div>
</div>
</blockquote><div><br></div><div>Yeah, and there's something funky with my profile. A clean profile works. It might have helped in my first reply if I had hit reply all, not just replied to Judah. I'll spend some time figuring out what bad extension(s) is/are the problem this week, so it can be wrote up, either as a bug, or as a notification to those extension authors, although, if extensions are nothing but JavaScript, then I would have to call that a bug.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">
Its working fine in MAC OS X.<br>
<br></div><div style="font-family:verdana,sans-serif">I tried e10s also works fine.<br></div></div></blockquote><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra">
<div><div class="h5"><br><div class="gmail_quote">On Sun, May 25, 2014 at 1:28 AM, Judah Richardson <span dir="ltr"><<a href="mailto:judahrichardson@gmail.com" target="_blank">judahrichardson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">New e10s window works just fine on my end. Loaded Facebook at Twitter in separate tabs in it. Which build are you using? I'm on 20140522030204.<div><div><br><div class="gmail_extra"><br><div class="gmail_quote">
On Sat, May 24, 2014 at 1:22 PM, Bryan Price <span dir="ltr"><<a href="mailto:bytehead@gmail.com" target="_blank">bytehead@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>On Sat, May 24, 2014 at 12:28 PM, Judah Richardson <span dir="ltr"><<a href="mailto:judahrichardson@gmail.com" target="_blank">judahrichardson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Actually, you can try Electrolysis now in the Win64 build by Alt -> File -> New e10s window. Assuming Win64 builds continue (hopefully less sporadically than lately), this brings Firefox on par with IE & Safari. All is not lost, there's still hope!<br>
</div></blockquote><div><br></div></div><div>Firefox has stopped working.<br><br></div><div>Not even a crash report. ;(<br><br></div><div>Or I'm laughing. I'm not sure which, yet.<br></div><div><div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, May 24, 2014 at 10:59 AM, Bryan Price <span dir="ltr"><<a href="mailto:bytehead@gmail.com" target="_blank">bytehead@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>On Sat, May 24, 2014 at 11:20 AM, Judah Richardson <span dir="ltr"><<a href="mailto:judahrichardson@gmail.com" target="_blank">judahrichardson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yeah I noticed that, but the last time we discussed this on here a new build came after a few days, so we'll see. I don't have anything to say about this issue that I haven't said already.<br>
<br>
The good news is that <a href="http://www.ghacks.net/2014/05/22/firefoxs-multi-process-architecture-becomes-priority-finally/" target="_blank">apparently Electrolysis now has a full team of people working on it</a>; some from the Metro team, no less. Gratifyingly this news comes <i>after</i> the aforesaid discussion, so <i>maybe</i> Mozilla is actually listening to us users. <br>
</div></blockquote><div><br></div></div><div>One can hope.<br></div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Sat, May 24, 2014 at 10:09 AM, Bryan Price <span dir="ltr"><<a href="mailto:bytehead@gmail.com" target="_blank">bytehead@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div>Our last update is May 22nd. Which, oddly enough, is the last date that has a date-time-Mozilla-Central directory that shows the compile time logs. So I don't know what's up with that. My 32-bit updated to today's date, and there is indeed a Win32 Firefox in the 2014-05-24-Mozilla-Central-Debug. But no 64-bit build. Going back, I don't see a 64-bit build in there in past dates, either.<br>
<br></div>Maybe there's some security issue that has made it such that they have turned off allowing Mozilla Central to the general public, which could mean that we are getting compiled, we just don't get the updates until they fix whatever the issue is.<br>
<br></div><div>I follow the developer's mail list, but I haven't seen this discussed. Which doesn't mean that it gets discussed there, either.<br><br></div><div>/sigh.<br></div></div></div></div></blockquote>
</div></div></blockquote></div></div></div></div></blockquote></div></div></div></div></blockquote></div></div></div></div></blockquote></div></div></div></div></div></blockquote></div></div></div></div></blockquote><br>
</div>
</div></div>