Earlier quoted context omitted.
Yes.
What about if you had pages open that you don't want to lose (literally hundreds of tabs)?
you can right click on a tab to bookmark all tabs to be safe.
Chrome for Mac 64-bit Support
51–60 of 84 posts
Re: Chrome for Mac 64-bit Support
#52If I have the 32 bit Chrome, do I need to install a new version, or will updates going forward give me the right architecture?
Mine just updated to version 39 and it got the 64-bit support.
Just to confirm, if I wait, the updater will grab version 39 x64 eventually, it just takes time to rollout.
Re: Chrome for Mac 64-bit Support
#53Re: Chrome for Mac 64-bit Support
#54Earlier quoted context omitted.
Yes.
What about if you had pages open that you don't want to lose (literally hundreds of tabs)?
> What about if you had pages open that you don't want to lose (literally hundreds of tabs)?
There's always one of these in every discussion about a web browser. That one person who, instead of bookmarking things, keeps literally hundreds of tabs open.
(Some of my best friends are "this guy")
Re: Chrome for Mac 64-bit Support
#55Earlier quoted context omitted.
I stopped using Chrome because of the java issue. It showed quite clearly that Google has zero regard for Mac users and their concerns
Not really. A lot of people at Google are on Macs. I think it's more that the Chrome team doesn't prioritize Java support, which I think shows their priorities are pretty much in order.
The "well, now that the last 32 bit app on your Mac gets with the times, life's gonna be better" comment shows (a) this wasn't just about Java, and (b) they knew they're way behind the times.
Re: Chrome for Mac 64-bit Support
#56Earlier quoted context omitted.
Not really. A lot of people at Google are on Macs. I think it's more that the Chrome team doesn't prioritize Java support, which I think shows their priorities are pretty much in order.
The "well, now that the last 32 bit app on your Mac gets with the times, life's gonna be better" comment shows (a) this wasn't just about Java, and (b) they knew they're way behind the times.
For one, it's far from the "ast 32 bit app" on the Mac.
Second, even some Apple apps took some years to be released as 64 bit after the transition.
Third, it's not like 64 bit apps get some magic cookies and unicorn love. Millions of Mac users used 32bit Chrome just fine and didn't even know about it (being 32bit).
Re: Chrome for Mac 64-bit Support
#57Earlier quoted context omitted.
Yes.
What about if you had pages open that you don't want to lose (literally hundreds of tabs)?
Then you should first change your browsing habbits, and probably several other ways in which you organize things in general. And ask yourself if you really understand modern technology.
Second, you could save all the open tabs as bookmarks, with the Bookmarks -> Bookmark all Tabs command. It will save all open tabs in a new bookmarks folder.
Lastly, when you reopen the browser after the update, you can click File -> Reopen closed tabs, which will reopen all of those, even if you haven't bookmarked them.
Re: Chrome for Mac 64-bit Support
#58Re: Chrome for Mac 64-bit Support
#59I 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.
FWIW, I'm on the beta channel and have been using 64 bit for a month or more with no issues or crashes whatshoever.
Re: Chrome for Mac 64-bit Support
#60Earlier quoted context omitted.
I think that for most purposes 32 bit had worked without much issue so it's a matter of cost vs benefit. Can you think of any issues that people face because Chrome was 32 bit? So far I'm seeing Java 8 integration, which is probably a tiny fraction of their users. Also it's not really breaking since those users can just use Firefox for that purpose. They obviously don't consider this a loss.
Security is a big one. 64-bit address spaces are inherently harder to exploit, plus, IIRC, on OS X in particular, ASLR in 32-bit processes has some weaknesses that were never fixed.
Good point! To stay on my angle, are there Chrome specific security bugs that are in the most recent builds that are exacerbated by 32bit builds?