Re:Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
by callahad on Wednesday April 19, 2017 @02:29PM
(#14150385)
The bitness choice (and that entire screenshotted dialog) is only present if you select "Advanced Options" in the bottom left of the installer's first screen, it's not something that we force every user through.
[ Parent
| on HN ]
Re:Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
by mrec on Wednesday April 19, 2017 @02:33PM
(#14150429)
Ah, OK, that makes more sense. Thanks.
What's the default if you don't select "Advanced Options", btw?
Re:Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
by callahad on Wednesday April 19, 2017 @02:45PM
(#14150543)
We're still defaulting to 32-bit on systems where both are supported, but we hope to default to 64-bit around Firefox 55. We had to delay this due to issues with Flash, sandboxing, and Farmville 2: https://bugzil.la/1317995
The tracking bug for making 64-bit the default is https://bugzil.la/1340936
Re:Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
by jbicha on Wednesday April 19, 2017 @03:01PM
(#14150705)
So I can blame Farmville for Firefox not being 64-bit by default on Windows? :)
Re:Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
by cpeterso on Wednesday April 19, 2017 @04:36PM
(#14151520)
Yes :(
Re:Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
by yuhong on Wednesday April 19, 2017 @03:17PM
(#14150848)
I dislike how the JIT don't comply with Windows x64 SEH requirements anyway. As a side note, I fixed NSS: https://bugzilla.mozilla.org/show_bug.cgi?id=1284375
Re:Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
by cpeterso on Wednesday April 19, 2017 @04:36PM
(#14151514)
Yuhong, is there a bug filed for the x64 SpiderMonkey JIT issues? What is the side effect of not following the x86-64 ABI for JIT code?
Re:Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
by yuhong on Wednesday April 19, 2017 @04:47PM
(#14151620)
SEH exception handling don't work properly and debuggers don't show a proper callstack. For it to work properly, the JIT has to generate "function tables" to allow Windows to do stack walking.