Oh, wow, didn't know that Chrome was still 32-bit on Macs. The Linux builds have been 64-bit since early 2009, and Windows went 64-bit earlier this year. Congrats to the Chrome team. :)<p>(FWIW, Firefox has been 64-bit on OS X and Linux since 4.0, but we're still working on Win64 support. Of course, Microsoft kicked everyone's ass when they released Windows XP Professional x64 Edition in 2005, which included a 64-bit version of IE6.)
This also fixes the Java 8 support in Chrome on Mac, which didn't work because Java 8 only supported 64-bit browsers:<p><a href="https://www.java.com/en/download/faq/chrome.xml" rel="nofollow">https://www.java.com/en/download/faq/chrome.xml</a><p>For those of us that still need to access legacy systems (routers, switches, etc.) that have Java interfaces, this is a pretty major upgrade.
So wait - I downloaded the 64 bit 39.0.2171.65 version. Because of this, I finally updated my Java version (now 8.25). I still can't java applets to run in Chrome. What gives? I still get Verify Java Version32-bit Chrome does not support Java 7 and later versions on Mac OS X. Java runs only on 64-bit browsers.<p><a href="http://javatester.org/version.html" rel="nofollow">http://javatester.org/version.html</a>
Gives an error - Java needs your permission to run, but I've already allowed in Java control panel. Ideas?
<p><pre><code> #73 mark@chromium.org
This was released to the stable channel today in version 39.0.2171.65.
Thanks for your patience, everyone.
Status: Fixed</code></pre>
<p><pre><code> damurdock$ file /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome: Mach-O executable i386
damurdock$ file /Volumes/Google\ Chrome/Google\ Chrome.app/Contents/MacOS/Google\ Chrome
/Volumes/Google Chrome/Google Chrome.app/Contents/MacOS/Google Chrome: Mach-O 64-bit executable x86_64
</code></pre>
Top is my currently installed Chrome, bottom is freshly downloaded from Google. Looks like it's time to update!
If you have previously installed Chrome via Homebrew Cask (<a href="http://caskroom.io" rel="nofollow">http://caskroom.io</a>), you can force an update to 39.x by running brew cask install google-chrome --force
Hopefully now they can resolve the issues that lead to Chrome having significantly less smooth scrolling than Safari and reducing the battery life of my MBP from ~8 hours to ~5 hours.
Finally! Tested and it works well with the Java 7 plugin. Somehow this Java verification page still doesn't work: <a href="https://www.java.com/en/download/installed.jsp" rel="nofollow">https://www.java.com/en/download/installed.jsp</a>
The requirement for 64 bit support for SSL VPNs has always required I live a hybrid world on the Mac - browsing with Chrome, and launching 64-bit firefox to connect to VPNs. It will be interesting to see if I can live in an all chrome world if I chose.
Just checking.. does the page <a href="https://dev.twitter.com/" rel="nofollow">https://dev.twitter.com/</a> load for those who've upgraded to the 64-bit OSX Chrome? Reliably crashes for me now..
Is this build more easier on the battery life? I tried Chrome Canary a few weeks ago and just scrolling down a page used up much more resources than Safari.
I was using 64 bit for about a week until only just a couple of days ago. It crashed often and in between crashes it kept popping up windows saying that pages were non-responsive (if I want to "wait" or "kill"). Some were actually unresponsive, others were responsive. Unless they fixed these major issues in only the last couple of days, I'm sticking with 32 bit.
Have they fixed the "Google Chrome Helper: CoreText CopyFontsForRequest received mig IPC error (FFFFFECC) from font server" error that has been around forever?