At least one person has updated Stable Chrome to Chrome 39 64-bit and tried to open the usual folder of 20 bookmarks - various blogs - and everything worked and seemingly more quickly than before. ;-) Myself. So go ahead.
Wasn't v39 supposed to disable sslv3 by default to mitigate the Poodle attack? I just downloaded 39.0.2171.65 (64-bit) for Mac and the poodle browser checks I tried show the browser is still vulnerable.
Re #3, thanks for the info - I'll check in on extension stability shortly.
Re #4, https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/Vnhy9aKM_l4/E0G5VPlb9B4J explains SSLv3 plans for Chrome. Can you let me know which POODLE checks you are using that are failing?
same as Darren Kruger, I download and use Chrome Mac 39.0.2171.65 (64-bit), but POODLE check show this Chrome is still vulnerable. check site: https://www.poodletest.com/ https://www.ssllabs.com/ssltest/viewMyClient.html
reset fixes the problem with crashing chrome using onetab. just have to go turn back on your extensions and custom appearance setting go back to standard.
error message when java tries to open in the new 64 bit version of chrome on mac Yosemite - not recognising it as 64 bit Below is the error message:- 32-bit Chrome does not support Java 7 and later versions on Mac OS X. Java runs only on 64-bit browsers.
If you download Oracle Java 7 and later versions, you will not be able to run Java content in Chrome on Mac OS X and will need to use a 64-bit browser (such as Safari or Firefox) to run Java content within a browser. Additionally, installing Oracle Java will disable the ability to use Apple Java 6 on your system.
Constant hard drive activity for about 1 or 2 minutes after opening with 8-10 tabs open. Very, very slow to respond until this activity stops. Still lagging due to HD activity sometimes after that. My wife's computer is the same. A month or so ago this wasn't the case. I have the 64-bit version 39, my wife the 32-bit version 38 (so far). Both computers are fine when Chrome isn't open. Is there a memory leak?
try -->reset fixes the problem with crashing chrome using onetab. just have to go turn back on your extensions and custom appearance setting go back to standard.
I'm still not getting the update via automatic updates (says 38 is up to date) and downloading from Google.com/chrome still gives me 38. What's the deal? I thought 39 for Mac was supposed to give 64-bit support. So where is it?
My Chrome is not vulnerable to the 'Poodle Attack' vai SSLv3. I am using Mac OS X Version 38.0.2125.122 OS X 10.9.5 (I am not using Yosemite). I'm not sure if i should update to 64bit version and risk being open to this type of attack. Safari runs more efficiently then Chrome would love to see if the 64bit version will help Chrome achieve the same type of performance.
My Chrome is not vulnerable to the 'Poodle Attack' vai SSLv3. I am using Mac OS X Version 38.0.2125.122 OS X 10.9.5 (I am not using Yosemite). I'm not sure if i should update to 64bit version and risk being open to this type of attack. Safari runs more efficiently then Chrome would love to see if the 64bit version will help Chrome achieve the same type of performance.
I suspect the devs haven't updated the page https://www.google.com/chrome/browser/ to point to the correct Stable Update yet (39). Same for me, i keep downloading the same 38 version.
I had to get mine from Techspot: http://www.techspot.com/downloads/4908-google-chrome-for-mac-os.html
Is it BETA, i have some probleme in set-up with the Win7, also The SSL certificate bug in this location voiture marrakech even if it's not part of it !!! @David "Add this to the target of the Chrome shortcut "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --ssl-version-min=tls1" i try it with no result.
Where do i report bugs? Since my chrome browser was updated to 39.0.2171.65 m it does ignore font-weight lighter. As a webdesigner it is very annoying.
My Chrome browser has auto updated to Version 39.0.2171.71 m I have always had the "Replace New Tab Page" 1.2 extension enabled. It is set to open https://www.google.com/webhp?complete=0&hl=en (as the homepage & new tab page) because I do not want my Google searches to be country specific. It has always worked perfectly until this Chrome update.
The extension is being overridden by something and is defaulting to Google.ca. REALLY annoying.
Initially after the update it would open to Google.ca and then when I clicked on the "new tab" it would open that one to Google.com.
However it is now opening the homepage + every new tab to Google.ca and nothing I do seems to fix it.
I have searched extensively to find the reason for this and have not come up with anything.
48 comments :
At least one person has updated Stable Chrome to Chrome 39 64-bit and tried to open the usual folder of 20 bookmarks - various blogs - and everything worked and seemingly more quickly than before. ;-) Myself. So go ahead.
Sweet! Was waiting for the stable 64bit Mac build. Thanks a lot!
Extensions seems to be crashing a little often now with 39 for some reason. :O
Wasn't v39 supposed to disable sslv3 by default to mitigate the Poodle attack? I just downloaded 39.0.2171.65 (64-bit) for Mac and the poodle browser checks I tried show the browser is still vulnerable.
Re #3, thanks for the info - I'll check in on extension stability shortly.
Re #4, https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/Vnhy9aKM_l4/E0G5VPlb9B4J explains SSLv3 plans for Chrome. Can you let me know which POODLE checks you are using that are failing?
Add this to the target of the Chrome shortcut "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --ssl-version-min=tls1
Does v39 deprecate NPAPI?
Is this available in Scheduled Release GAFE domains yet?
Mac升级到了优胜美地,依然舍不得chrome,你再不发布64bit版本,我就要转投safari了!
How come beta version 39.0.2171.62 beta-m (64-bit) lags after the stable version ?
Does the support for XSLT is dropped on this version?
same as Darren Kruger, I download and use Chrome Mac 39.0.2171.65 (64-bit), but POODLE check show this Chrome is still vulnerable.
check site:
https://www.poodletest.com/
https://www.ssllabs.com/ssltest/viewMyClient.html
Looks like this fixed some of the issues we had where Chrome is hanging
Am i the only one who's not getting this update ? I'm located in Romania (Yosemite) and for some reason going to About, Chrome says it's up to date..
@madalin - I had the same problem. You need to get Chrome from its download page. Once installed you should be on v39 (64-bit).
@Paul: well this sounds like a bug ?:)
@Paul right after the posting of the bug comment before, it looks like it's updating now.. :)
In version Google has process of sunsetting SHA-1.
http://googleonlinesecurity.blogspot.co.il/2014/09/gradually-sunsetting-sha-1.html
reset fixes the problem with crashing chrome using onetab. just have to go turn back on your extensions and custom appearance setting go back to standard.
I've lost hardware acceleration on PPAPI flash video on YouTube. NPAPI works.
Chrome auto update is not working. "About Google Chrome" is saying, "Google Chrome is up to date." at version 38
error message when java tries to open in the new 64 bit version of chrome on mac Yosemite - not recognising it as 64 bit
Below is the error message:-
32-bit Chrome does not support Java 7 and later versions on Mac OS X. Java runs only on 64-bit browsers.
If you download Oracle Java 7 and later versions, you will not be able to run Java content in Chrome on Mac OS X and will need to use a 64-bit browser (such as Safari or Firefox) to run Java content within a browser. Additionally, installing Oracle Java will disable the ability to use Apple Java 6 on your system.
Is this faster than Canary
Chrome 39 crashes on launch for me. Mac Mini late 2012 running 10.10.1
I have to switch to Safari until Google solves.
Constant hard drive activity for about 1 or 2 minutes after opening with 8-10 tabs open. Very, very slow to respond until this activity stops. Still lagging due to HD activity sometimes after that. My wife's computer is the same. A month or so ago this wasn't the case. I have the 64-bit version 39, my wife the 32-bit version 38 (so far). Both computers are fine when Chrome isn't open. Is there a memory leak?
My Chrome is not auto-updating. Has this update been pulled?
I have the About page open, I've tried refreshing 20 times, I've tried just waiting, I've restarted my Mac. Nothing.
Do a fresh install to get the mac 64bit,it works for me
I think it can't do it by auto-update.
Best update. improved a lot. thanks to the developers for you hard work. Credit to you!!!
chrome beta still
Version 39.0.2171.62 beta-m
(32-bit, 64-bit)
I'm lovin the fix to the cpu timer resolution, its giving me another hour of battery life on my laptop!
try -->reset fixes the problem with crashing chrome using onetab. just have to go turn back on your extensions and custom appearance setting go back to standard.
Surely there is a tool to detect use-after-free. At the rate end users find them, there must be hundreds more ripe for exploitation.
This is Will be very interesting. http://haviafotokopi.blogspot.com/
High Quality Calls for Technical Support @ 9811420083
Bing Ads PPC For Tech Support
Google Adwords For Tech Support
PPC Management Company
I'm still not getting the update via automatic updates (says 38 is up to date) and downloading from Google.com/chrome still gives me 38. What's the deal? I thought 39 for Mac was supposed to give 64-bit support. So where is it?
Me too, I cannot update or install 64bit either, sure there is a 39 update stable for Chrome?
same here, Yosemite stuck at 38, and download from google.com/chrome still gives me 38 too
Same here. Stuck on 38 on Yosemite. Download/replace and delete/download/replace all same result
I also don't get Chrome 39. I tried uninstalling and installing again but it is still 38. My CPU is 64-bit since it Intel i5.
My Chrome is not vulnerable to the 'Poodle Attack' vai SSLv3. I am using Mac OS X Version 38.0.2125.122 OS X 10.9.5 (I am not using Yosemite). I'm not sure if i should update to 64bit version and risk being open to this type of attack. Safari runs more efficiently then Chrome would love to see if the 64bit version will help Chrome achieve the same type of performance.
My Chrome is not vulnerable to the 'Poodle Attack' vai SSLv3. I am using Mac OS X Version 38.0.2125.122 OS X 10.9.5 (I am not using Yosemite). I'm not sure if i should update to 64bit version and risk being open to this type of attack. Safari runs more efficiently then Chrome would love to see if the 64bit version will help Chrome achieve the same type of performance.
I suspect the devs haven't updated the page https://www.google.com/chrome/browser/ to point to the correct Stable Update yet (39). Same for me, i keep downloading the same 38 version.
I had to get mine from Techspot: http://www.techspot.com/downloads/4908-google-chrome-for-mac-os.html
The file size should be 63 MB, not 60MB.
Thankssss! Java 7 was killing me!
Chrome 39 from google servers:
https://dl.google.com/chrome/mac/stable/CHFA/googlechrome.dmg
Is it BETA, i have some probleme in set-up with the Win7, also The SSL certificate bug in this location voiture marrakech
even if it's not part of it !!!
@David "Add this to the target of the Chrome shortcut "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --ssl-version-min=tls1" i try it with no result.
Where do i report bugs? Since my chrome browser was updated to 39.0.2171.65 m it does ignore font-weight lighter. As a webdesigner it is very annoying.
My Chrome browser has auto updated to Version 39.0.2171.71 m
I have always had the "Replace New Tab Page" 1.2 extension enabled. It is set to open https://www.google.com/webhp?complete=0&hl=en (as the homepage & new tab page) because I do not want my Google searches to be country specific. It has always worked perfectly until this Chrome update.
The extension is being overridden by something and is defaulting to Google.ca. REALLY annoying.
Initially after the update it would open to Google.ca and then when I clicked on the "new tab" it would open that one to Google.com.
However it is now opening the homepage + every new tab to Google.ca and nothing I do seems to fix it.
I have searched extensively to find the reason for this and have not come up with anything.
Post a Comment