Downloads
Updates:
1/25: Firefox 3.7 Alpha 1 Pre posted.
1/21: Firefox 3.6 FINAL posted.
12/28: Firefox 3.5.7 posted (Snow Leopard only).
11/18: Firefox 3.7 32-Bit Alpha 1 Pre posted.
8/9: Camino 2.1 Alpha 1 Pre posted.
I’ll be posting the latest builds of various projects to this page rather than updating each article with the new builds. Comments are ON so if you have any feedback, lemme have it.
Also, the normal naming convention for beta and RC builds is to use a “pre” status. For example beta 4 was 3.5b5pre. All RC candidates have been 3.5pre.
Firefox 3.7 64-Bit (Snow Leopard)
See Related Post
- Download 64-Bit Minefield 3.7 Alpha Pre 1 dmg
- mozconfig_sl.tgz (newest mozconfig for Snow Leopard)
Firefox 3.7 32-Bit
Firefox 3.6
See Related Post
Firefox 3.5.7 (Snow Leopard)
Firefox 3.5.6 (Snow Leopard)
Firefox 3.5.5 (Snow Leopard)
Firefox 3.5.4 (Snow Leopard)
Firefox 3.5.3 (Snow Leopard)
Snow Leopard only. This will crash on anything earlier (I’m investigating).
Firefox 3.5.2
See Related Post
- Download Intel Optimized Shiretoko 3.5.2 dmg
- mozconfig.tgz (this has not yet been updated for Snow Leopard)
Camino 2.1
See Related Post
OSX Chrome
See Related Post
Comments RSSComments
Hi,
Does the 3.5pre download reflect the latest firefox build (in the case 3.5 RC3?)
It is difficult to check the build number.
Thanks
jack
This is indeed RC3. The build names for all RCs so far have been named the same - 3.5pre.
The final release is coming tomorrow, but I can now see it in the Mecurial repository. I'll wait until the official announcement before doing the final build.
What is the difference between your builds and the ones found here: http://firefoxmac.furbism.com/ Are they both optimized for the Mac?
Seems they only have PPC optimized builds. I only have Intel optimized builds.
Also, I've spent a ton of time working on the optimization with help from contributors and even Mozilla employees. I'm told, my build is the fastest Intel optimization out there.
nice build, works fast for me
hmmm, but one thing that bugs me is that facebook does not recognize that the browser is running on a firefox engine, so certain functions are down (i.e. toolbar chat). that doesn't happen with other builds i've tried like ElFurbe's, so i'll be using that for now…
still do keep updating your build and i'm always ready to give it a place in my mac
You can use a plugin like User Agent Switcher to change your agent to "Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5" for sites like Facebook.
I made a minor modification to the UA string, but didn't think it would have this kind of effect. I will repost with the standard UA.
Done!
Let me know if it works any better for you.
@chris: hmmm it still doesn't seem to work with facebook… maybe you missed out something?
@matt: your suggestion works great! think i'll be using this for now until chris fixes the UA issue.
thanks guys
@chris: i just tried downloading shiretoko again, but my user agent is still
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1pre) Gecko/20090630 Shiretoko/3.5.1pre AutoPager/0.5.2.2 (http://www.teesoft.info/)
did i download the old version?
@matt: yup the addon works great! will be using this until the UA issue is corrected.
thanks for the help guys!
That is the newer version. My machine is under heavy load today so I can't do another build until I have more resources (probably tomorrow).
What are the chances of there being a 64bit build?
hi chris, realised that the problem can easily be corrected on my part by editing the preference "general.useragent.extra.firefox". thanks for this build, it works superbly with this UA problem out of the way!!
I've figured out how to remove the pre in the milestone (1.9.1) and browser (3.5.1) so have uploaded a new build. This really wasn't documented anywhere, so had to dig through the source to figure out these designations rely on static config files.
I just download this and could no longer use the (relatively) new version of yahoo mail. It only supports the classic version.
I didn't know this version still existed! I was very happy back in Firefox 2.0, I'll give it another try!
Now that Snow Leopard is out, I'd also appreciate a 64-bit build.
Thanks for the great support!
Currently it isn’t possible to build any of the Gecko projects in 64-bit. I’ve tried and discovered through experience and research that it is not possible. Firefox 3.6 is planned to be 64-bit, but the current trunk is not there yet. As soon as is possible, I’ll begin with 64-bit builds.
I previously did some 64-bit WebKit build, pre-Snow-Leopard, but these had no performance increases so I did not release them.
Thanks a lot for your great releases but this time there's an issue:
When starting up Intel Optimized Shiretoko 3.5.3 permanently crashes with
OS Version: Mac OS X 10.5.8 (9L30)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0×000000008b084589
Hope that helps fixing it and looking forward to a new release,
Jo
Thanks for the info. I've only been running it on Snow Leopard and have had no issues. I'll post a warning.
Thank you for this excellent browser. I am using Shiretoko 3.5.2 and it doesn't work with Google Desktop Search. very weird. Could you please make them work together.
You should be able to use it just fine by changing the general.useragent.extra.firefox to something like Firefox/3.5.3 in about:config
3.7 64-bit fails on SL 10.6.1 (for me anyway) It complains about sqlite being too old. Mine is sqlite3 3.6.18.
My apologies to you and everyone else. I hacked up my own patch for the sqlite problem. The build worked, but no matter what I did, the wrong libsqlite was getting pulled into the packager. I've applied the official patch and now all is good.
The about:config method does not work.
At least, not entirely.
Someone said it was actually working correctly, that it is Safari & Firefox which are working improperly. But that seems rather doubtful, especially as it is supposed to be the same/similar to Firefox…
The colors remain washed out in the font, background & most pictures.
I made a change to the about:config that considerably increased the download speed, however, the setting was lost & I do not remember what it was. It may have been some sort of cross~check. Still, I am surprised that such a significant change is not more widely known, if not implemented. It is listed on one page somewhere on the Internet.
The Minefield/3.6a2pre works on 10.4.11 Intel, but many of your other versions do not.
I, generally, use Camino & Firefox~ your version seems to work better than most~ & sometimes Safari. But Safari seems to cause a lot of trouble. It does download fast & have a few other nice features. I believe the ‘larger construction’ ‘Webkit’ is broken on my computer & I can only use the ‘independent browser’. I use a 4~ either one or the other with the different history styles & tab configurations. I have taken to drag~and~drop for Camino a lot of times. Using ClipEdit allows better use of .textClippings.
Sometimes, I use the Sun Download Manager.
I've tried both the 3.5.7 build and the 3.7 64-bit, there appears to be a problem with the xml parser; I get the following error when visiting a skydrive site:
XML Parsing Error: not well-formed
Location: http://cid-03c77915e8230e36.skydrive.live.com/bro...
Line Number 76, Column 184: <div id="m_wh"><script type="text/javascript">/* Copyright (C) 2009 Microsoft Corporation */function $c_TreatTile(a,e){a.style.display=e;var d=a.width,c=a.height,b=19;if(d>=c||c<b)a.height=b;if(d<c||d<b)a.width=b}</script>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------^
Congrats on the 64-bit build, are you planning on building 64-bit 3.5.X version?
Hmm. Odd. I haven't heard of the XML problem before. Looking at that page, I do get a parse error on that page, but I'm going to blame it on this build being Engligh only. Other than this, I've been using 3.7 as my primary browser for the past month or so, using almost daily builds, without problem.
3.5 will not be 64-bit, neither will 3.6. I'll work on a GCD version of 3.7 in the new year. That will probably take me a little while though.
It does not seem to be a language/character encoding issue. Just going to skydrive.com causes the XML parsing error.
flash is not working for me on snow leopard
Dear Cris, I love the speed of the 64 Bit Build, but
I was missed all my favorite add ons and plug ins. So
I went to your latest 3.6 Build.
Keep up your good work and perfecting Minefield and I
will explore social media and checking in with Josh and You
Pax
Br. Dan
2008 iMac with 4Gigs of Ram running Snow Leopard.
@ MATT
try 64Bit Prerelease:
http://labs.adobe.com/downloads/flashplayer10.html
@BLA
Flash 10.1 is not 64-bit:
$ file /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/MacOS/Flash\ Player
/Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player: Mach-O universal binary with 2 architectures
/Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player (for architecture ppc): Mach-O bundle ppc
/Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player (for architecture i386): Mach-O bundle i386
Wow, you’re really fast with pushing out these builds! You beat even mozilla! I appreciate it. Thanks!
--
http://vastlife.wordpress.com
http://twitter.com/vastlife
After doing a few tests, I don’t see any speedup (running SunSpider) with the 64bit build of 3.7 vs. Mozilla’s nightlies (available http://nightly.mozilla.org).
Pretty sure that PGO is only available with Intel’s C-compiler which weren’t used for these builds. There may be a slight improvement for some operations due to restricting to the later SDK, but otherwise I think these builds are actually inferior to Mozilla’s released builds.
Mozilla spends a lot of effort working on optimal build-settings. Setting optimizations at the top-level can affect sub-module performance as some of them work better with different settings.
but, YMMV. Happy hacking.
@Rob
You are probably right about no speed difference between the 64-bit and nightlies using sunspider. I used to build 64-bit WebKit before it was officially launched and that made no difference.
What I do see in the browser is increased launch times, faster page rendering, greater stability. All of this is subjective so could be my imagination.
Other things:
1) I do mess with the mozconfig to try to get faster performance and have gone overboard more than once. So you aren’t going to see the most stable builds here.
2) I mess with preferences after compiling that I feel makes the browser faster and people may or may not like these changes.
3) I don’t have the greatest grasp of optimization trickling through to submodules. This is why I put my mozconfig out there so people can provide feedback.
Thanks for the feedback.
hi again. Just to clarify the PGO option, I asked someone who knows more about these things than I do and he said, “gcc supports PGO, but it’s not very good, generally”. So there might be some win there, but I’d expect it to be pretty small.
I did get the impression that windows and tabs were opening pretty quickly, so there could be some SDK-related wins, but without measuring it, I feel like I’m fooling myself.
anyway, just throwing that stuff back at you. I didn’t look at your prefs to see what you were doing post-build, but I’ll take a look. If anything jumps out, I’ll post back (and if anything looks like it might make a difference, I’ll be sure to mention it to my friends in moz-werld).
After spending some time checking results and build options with colleagues and running this through a part of our performance analysis tool (talos), I can say that the biggest performance gain obtained from the settings in your mozconfig for 3.7 is the targeting against the 10.6 SDK. We were seeing roughly a 5% speedup for startup times and a couple of points for tab opening. It’s possible there are some other improvements around related to the newer optimized SDK, but I don’t think the other options are providing much.
You can see the numbers from my analysis here:
https://bugzilla.mozilla.org/show_bug.cgi?id=542095