Chrome Releases

Release updates from the Chrome team

Stable Channel Update for Desktop

Thursday, December 14, 2017
Share on Google+ Share on Twitter Share on Facebook
Google
Labels: Desktop Update , Stable updates

13 comments :

Mike T said...

Not able to connect to banking site

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36

Steps to reproduce the problem:
1. navigate to bank website

What is the expected behavior?
should load bank website homepage

What went wrong?
This site can’t provide a secure connection
www.xxxxxx.com sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

Did this work before? Yes 62.0.3202.94

Chrome version: 63.0.3239.108 Channel: stable
OS Version: Linux Mint 17.3 Rosa 4.4.0-45-generic #66~14.04.1-Ubuntu x86_64 GNU/Linux
Flash Version: Flash Version: 27.0.0.187

When I attempt to log in to mail.aol.com

Chrome presents a page that displays:
-------------------------------
This site can’t be reached
The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET
-------------------------------

Before updating from 62.0.3202.94 - the page to login would load

This behavior started after updating to Chrome version: 63.0.3239.84 : Stable and persists in 63.0.3239.108

Firefox 57 continues to load these pages properly

When I re-install google-chrome-stable_62.0.3202.94-1_amd64.deb - I am able to access those sites that failed to connect after the updates ...

Which now include 39 security fixes

When thomasanderson@chromium.org last logged into https://bugs.chromium.org/p/chromium/issues/detail?id=793679 where I report that google-chrome-stable_63.0.3239.84 had impaired my ability to log into various sites - he asked me to bisect the issue and posted terminal commands with a link embedded - but did not explain that those commands would open a Chromium browser window, or that the python tool would also be transmitting data from my PC to ?google?...

Nor did he respond when I asked for guidance regarding the Chromium window or the fact that the terminal was apparently waiting for data from the Chromium window - after I closed the Chromium window, the teminal window resumed with this:

Revision xxxxxx is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]:

https://bugs.chromium.org/p/chromium/issues/detail?id=793679 current status is WontFix - and shows as being closed as of Dec 11

I hope that this report will be addressed more effectively - in the meantime - I guess I have no choice but to use Firefox until the chrome team can properly address the issues described

3:53 PM, December 14, 2017
igorponger said...

63.0.3239.108
Beware of a huge Bug !!!!!!

Can't close the Coocies Settings popup menu/ There is no "cross" sign (shown in red) on the menu.
Please take care to introduce the "cross" on the top corner of the menu panel .

Thanks.

http://mytabletennis.net/forum/uploads/14298/pop_up.jpg

5:44 AM, December 15, 2017
htc zeggis said...

Updated my Chrome, but all my rtmp videos are stutter on my website now and before there was no stutter:( i tested in Microsoft Edge and explorer 11 and no stutter in there, i reset Chrome but still got this stutter problem:(

i'll wait for a fix:)

8:21 AM, December 15, 2017
Krishna Govind said...

igorponger & htc zeggis, could you pls report a separate bug under crbug.com and provide all details (OS, Chrome version) there? Thank you.

11:13 AM, December 15, 2017
abu ibrahim said...

Is not support yet show side bookmanager like other browser ):
still feel bad about bad

8:57 PM, December 17, 2017
Crankcase08 said...

Updated Chrome to 63.0.3239.108 yesterday, and now I can't access any websites without doing a refresh. Just about every update brings a new problem. It's about time Google employed developers who can do their jobs properly rather than spending their days stuffing Mars Bars and pizza into their mouths.

9:14 AM, December 18, 2017
Andrew Sergeev said...

When i send post request from Google Chrome extension in new browser version (Google Chrome v63.0.3239.108) i get the status code 302 (redirect for login page)

I try read Google Chrome changelog, but it's not help me to fix this problem. What can i do? or it's bug in new version of Chrome?


https://stackoverflow.com/questions/47882742/send-post-in-chrome-extension-google-chrome-v63-0-3239-108

12:29 AM, December 19, 2017
Petter Berg said...

Experienced multiple times daily that the CPU goes up to 100%. Anyone else who experiences this?

3:08 AM, December 20, 2017
iktinos said...

Since i updated to Version 63.0.3239.108 , i get mem usage close to 85%, and it crashes everything

2:18 PM, December 20, 2017
narucy said...

since Ver 63.0.3239.108 (Windows 10 with dual monitor, GTX1050 graphics) window moving across monitor to address-bars, buttons, bookmark-bars are filled to black.

Recorded:
https://www.youtube.com/watch?v=ubDu-AH5CCw

It's annoying, I need to roll back previous version.

6:33 AM, December 21, 2017
Alex Vernacchia said...

We are having an issue with the most recent release, 63.0.3239.108, when using popups to go through the authentication flow for google adwords.

Our flow going like this:
1. open a popup
2. redirect to google adwords authentication page
3. user logs in and is redirect to our redirectUrl with a code
4. we check the popup on an interval looking for this code
5. once we see the code we close the popup and proceed on our merry way.

Since the release above, we cannot go through this flow anymore. This seems to be due to the fact that after we redirect away from our origin, the user logs in, and they are redirected back to our URL, we can no longer access the popup's location.href. We get the following error.

[Exception: DOMException: Blocked a frame with origin "https://localhost:5000" from accessing a cross-origin frame. at checkPopup (https://localhost:5000/2.audiences.js:3018:16)]

As you can see, the places trying to access one another are on the same domain, meaning there should be no cross-origin problems.

Our pseudo code looks like below:

popup = window.open()
popup.location.href = 'google adwords auth page'

setInterval(() => {
// wait for user to login and get redirect to the redirect URL with the code designating successful auth
var urlWithCode = popup.location.url // this is where we get the error mentioned above

}, 100)

This is a huge problem us at Salesforce and stopping our customers from connecting google adwords accounts

8:54 AM, December 21, 2017
KajMagnus said...

@Alex Vernacchia, I think I'm having the same problem. I'm also using popups for login, and this recently broke, in Chrome (I now use version 63.0.3239.108). But stil works fine in Firefox. Previously, worked fine in Chrome too.

What doesn't work, is: An iframe with embedded comments, origin https://example.com, opens a popup window, the same origin. Inside the popup, the user clicks "Login with Google". Now, the popup loads Google's login page, on Google's domain. Thereafter, after the user has logged in, the popup redirects back to https://example.com. And now some code in the popup, attempts to tell window.opener that login succeeded. But when it does this, by sth like calling window.opener.continueAfterLogin(), there's an error: "Blocked a frame with origin http://example.com from accessing a cross-origin frame" — although both the iframe, and the popup, have the same origin.

I'm wondering if this is a Chrome bug, or if it's the intended behavior?

I'm thinking about working around this, by closing the popup, and instead in the iframe (i.e. the popup's window.opener) poll the cookies list, and when a session cookie suddenly appears in the iframe, call continueAfterLogin().

And, right now, login with Google is a bit broken, for this embedded commenting system, in Chrome.

12:23 AM, December 25, 2017
Sm nodame said...

lost focus of the textbox that is in the popup when try to make request to server with interval

5:33 AM, December 27, 2017

Post a Comment

  

Labels


  • Admin Console
  • Android WebView
  • Beta
  • Beta updates
  • chrome
  • Chrome Beta for Android
  • Chrome Dev for Android
  • Chrome for Android
  • Chrome for iOS
  • Chrome for Meetings
  • Chrome OS
  • Chrome OS Management
  • Chromecast Update
  • Desktop Update
  • dev update
  • Dev updates
  • Flash Player update
  • Hangouts Meet hardware
  • Stable updates


Archive


  •     2018
    • Apr
    • Mar
    • Feb
    • Jan
  •     2017
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2016
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2015
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2014
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2013
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2012
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2011
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2010
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2009
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2008
    • Dec
    • Nov
    • Oct
    • Sep

Feed

Googleon Google+
Follow

Company-wide

  • Official Google Blog
  • Public Policy Blog
  • Student Blog

Products

  • Android Blog
  • Inside Search Blog
  • Lat Long Blog

Developers

  • Developers Blog
  • Chromium Blog
  • Android Developers Blog
  • Google
  • Privacy
  • Terms