Got it automatically on OS X Yosemite, but not on OS X Mavericks (simply downloaded it and installed myself).
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Chrome for Mac Gains 64-Bit Support in Latest Chrome 39 Update
- Thread starter MacRumors
- Start date
- Sort by reaction score
Much snappier than Safari 8.0 that's my experience on a ADSL2+ router.
The 38 beta versions of Chrome were also snappier than Safari. So for me Chrome it is
64bit personal computing was first released on the PowerMac G5 in the summer of 2003.
What were you doing in June 2003?
Scrolls smoothly for me on OS X and Windows 7.
Load the verge or another graphic heavy site and scroll in Safari and Chrome. Inertia is much smoother in Safari.
Do you even know what the difference is between a 32-bit app and a 64-bit one? No, I don't you do or you wouldn't make such a ridiculous moot comment as there is no appreciable difference for this type of app beyond a tiny bit of RAM (which can backfire as well for many apps since 64-bit addressing requires more ram to be allocated, not less).
People think of the improvements they got when their processors jumped from 8-bit to 16-bit to 32-bit to 64-bit, but that doesn't mean Apps somehow run better. For most apps the memory addressing is the only real difference. 64-bit Photoshop can open larger than 2GB image files. It makes sense to use it if you deal with huge photos. WTF does Chrome do that "needs" 64-bit? Nothing, really. But Apple may end support for 32-bit Apps in the future so they are smart to switch, but to the end user for most programs that don't need more than 2GB of ram to function, it means JACK SQUAT.
Just to followup, turns out it was GlimmerBlocker causing the problem. Despite working on Safari and previous versions. Turning GlimmerBlocker off and loading Chrome then turning it back on resolved the issue. I also think adding 127.0.0.1 to have it ignore using the proxy may also keep 1Password working.
I know of several honestly. Safari user base is so small it does not even make it on a lot places test list. So any one off issues in Safari are not touched. The official answer is "we recommend you use Chrome FF or IE."
Wow, hilarious that this myth is still floating around. Ignorance knows no bounds on the internet. There's not much point discussing this with you further, as you're just reciting 2006 talking points. When you demonstrate that you actually know something about CPUs we can talk.
It happens to me as well. Websites just hang sometimes and takes a long time for the site to connect
They did. You can't even just delete history, you have to delete history and all website data at the same time. Ludicrous.
OT, I seem to remember that there was a way to switch safari from 64 bit back to 32 bit (there was an issue with an older OS). How exactly did we do that or does that option not exist anymore?
I'm only asking because I don't know if I ever switched it back to 64 bit
I used to use Chrome a lot, even in Mac, it's so convenient, all these bookmarks and add ons, sync them between PC/Mac even mobiles.
After upgraded to Yosemite, I switched to Safari, chrome sometimes makes the Mac fan running, I think that is the reason I switched to Safari, though lack of these add-ons
After upgraded to Yosemite, I switched to Safari, chrome sometimes makes the Mac fan running, I think that is the reason I switched to Safari, though lack of these add-ons
Sunspider 1.0.2, lower-->better
FIREFOX - ca 130-150ms
NEW CHROME 64bit - ca 220ms!!!!
OLD CHROME 32bit - ca 160-170ms
Safari 7.1
the whole benchmark takes much longer than on other browsers, but score is very good:
============================================
RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total: 148.3ms +/- 4.0%
--------------------------------------------
Had to manually download and install the latest update on my 10.9.5-equipped MBP. That's not a bad thing, though, as I needed to update the backup copy I keep in case of a system reinstall or upgrade.
So far it's working extremely well. I'm noticing a definite speed improvement, and no issues with any of my extensions either.
So far it's working extremely well. I'm noticing a definite speed improvement, and no issues with any of my extensions either.
Well, some might claim it's easy to pull a rabbit out of their back side, but without any PROOF of this rabbit, I might as well just assume they're really just taking a dump.
I agree with your statement about IGNORANCE on the Internet. Your post has convinced me it's true.
Last edited:
Any idea what it is? I've heard it suggested that it's used only when selected corrupted video files in the Finder, since it needs to try old codecs to preview it, but that wouldn't explain the Safari aspect. Other than a few instances of that strange process, Microsoft Office 2011 and Dropbox are the only remaining 32-bit processes I run by default now that Chrome has been updated.
If Safari or plugins use the QTKit.framework (QuickTime framework), then Safari starts a separate process, because QuickTime has a lot of potential vulnerabilities.
Quicktime plugin missing
Can anyone playback quicktime videos in the 64-bit chrome? I tried playing back a trailer and a video on the apple site and neither works. For example, can anyone play this video back?
http://www.apple.com/watch/films/#film-design
Any ideas on how to get the QT plugin to show up and work?
Can anyone playback quicktime videos in the 64-bit chrome? I tried playing back a trailer and a video on the apple site and neither works. For example, can anyone play this video back?
http://www.apple.com/watch/films/#film-design
Any ideas on how to get the QT plugin to show up and work?
Pioneer of everything? Wasn't Chrome originally built using Apple's Webkit?
Last edited:
Not from us. Apple will have to release a 64-bit QT plugin for the 64-bit browsers to be able to play quicktime videos.
Not quite Apple's WebKit, although Apple's certainly contributed a good amount to it (as Google now has since introducing Chrome).
Do you actually use Safari in Yosemite? It doesn't load pages half the time and it slow. I've normally used Safari as my daily driver, but since all the performance issues I've made the switch.