Rodze wrote:IETab uses its own plugin, which I guess only works on 32 bit Firefox. You'll have to ask the extension developer to see if 64 bit Nightly is / can be supported.
As you've read, the 64 bit version of Flash comes with both the 32 bit and the 64 bit plugin. Maybe Adobe only includes a 32 bit .exe of the configuration manager -- just guessing. The point is that it works. =P
Maybe Mozilla will care about saying its the 64 bit of Firefox when they start to release 64 bit versions of Firefox, but you can file a suggestion bug on bugzilla I guess.
Thanks for your comments. The two "negative" issues are really not show stoppers, and I agree about your Flash observation -> "The point is that it works. =P"
Thanks again.
Although every day is Judgment Day, I nonetheless feel like a room without a roof.
I don't think anyone knows what's wrong with them right now. Usually working around PGO bugs means "find out where the broken assembly is", then "figure out a way to rewrite or rearrange the relevant source code to generate non-broken assembly". If that sounds vague, it's because it is. You can't fix these issues so much as work around them because really, as far as we know, it's a bug in Microsoft's Visual Studio compiler - not a bug in Mozilla code. You can complain to Microsoft's Visual Studio team, but unless you can reverse engineer exactly what's going wrong and how to fix it, your only real recourse is likely to hope that it's fixed in the next iteration of Visual C++.
Someone with experience working on compilers might be able to tell you why these kinds of bugs happen, but really it's just a case of [trigger astronomically rare edge case] -> [produce broken code].
Last edited by Ver Greeneyes on September 30th, 2012, 10:06 am, edited 2 times in total.
JoeG wrote:It worked two days ago; it's broken today. This means something I did yesterday caused a problem.
What am I missing?
Display-List Based Invalidation (bug 539356) is what caused the problem. Thing is, it's not that the code is broken (because it works on non-PGO builds) but that it causes a pre-existing compiler bug to rear its ugly head. Since 64-bit Windows builds are not a first tier platform, however, I guess they opted to disable updates to those builds rather than backing out DLBI while they look for a workaround.
Anything definitive on the performance of 64-bit vs 32-bit? I'm on 64, but am considering switching to 32 so I can use the Google Chat plugin. However, I wouldn't use it often, so even a mild performance benefit from 64 would warrant me keeping it.
"Know what I pray for? The strength to change what I can, the inability to accept what I can't, and the incapacity to tell the difference." -Calvin
Bill Gianopoulos wrote:2012-09-30 11:00:02 PDT ... > If as said in previous comments, this is PGO only, I think the correct way > forward here is to not have the Nightly win 64-bit Nightlies be PGO builds.
I meant to say until we figure this out, of course.
It's fascinating how complicated all this is. It really makes me wonder how they managed to get "Curiosity" to take pictures of rocks on Mars. Of course NASA has lots more money, but their task appears to be proportionally more complicated.
Although every day is Judgment Day, I nonetheless feel like a room without a roof.
Caspid wrote:Anything definitive on the performance of 64-bit vs 32-bit? I'm on 64, but am considering switching to 32 so I can use the Google Chat plugin. However, I wouldn't use it often, so even a mild performance benefit from 64 would warrant me keeping it.
32bit is supposedly faster as it has more optimization and is more of a focus - i thought 64bit was only really good if you like FF to use more then 4 gig of RAM per session?
Micro gaming box: AMD A10-7800 APU, 8gb RAM M350 ITX case (size of a book), Windows 10/Ubuntu Tablet/Laptop: Asus Transformer T100, Intel Atom 2GB RAM, Windows 10 x86 Mobile:Xiaomi Redmi Note 3 Pro
32bit is supposedly faster as it has more optimization and is more of a focus - i thought 64bit was only really good if you like FF to use more then 4 gig of RAM per session?[/quote]
Mozilla seems to pay more attention on 32-bit - BIG true - but lastest 64 builds have been very fast(er). If you run JS-tests the 32bit are still slightly faster than 64, but the 64 versions FEELS way snappier (startup is also faster than 32) - that's my impression. Like several has mentioned, since Sep 28 the 64 with PGO are broken, but you can dl 64-PGO versions up to Sep 27 who's works perfect.
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.
)
