Wednesday, January 27, 2016

Stable Channel Update

The stable channel has been updated to 48.0.2564.97 for Windows, Mac, and Linux.

A list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.


Krishna Govind
Google Chrome

Labels:

19 Comments:

Anonymous Anonymous said...

WTF GOogle, beta channel 48.0.2564.82, but stable 48.0.2564.97???

3:15 PM, January 27, 2016  
Blogger Ermeson said...

WTF GOogle, beta channel 48.0.2564.82, but stable 48.0.2564.97???

4:41 PM, January 27, 2016  
Blogger Red Chamber said...

WTF GOogle, beta channel 48.0.2564.82, but stable 48.0.2564.97???

5:25 PM, January 27, 2016  
Blogger Victor said...

Under the File Command, Email page location doesn't work anymore.

6:03 PM, January 27, 2016  
Blogger Luca Schiavoni said...

I have used the beta version for a while on Mac and it crashes quite frequently.
So I switched to the stable channel, but that also seem to crash quite a lot.

I used Windows until a few weeks ago and all these crashes weren't happening - I guess there's a serious stability problem with Mac versions?

6:04 PM, January 27, 2016  
Blogger Whateverman said...

Wow. The update/reload Chrome button actually worked for the first time in a year or more. Usually it just closed Chrome and I had to manually re-open, but it actually relaunched all on its own. Something was fixed!

5:49 AM, January 28, 2016  
Blogger Eric Ahnell said...

@Dragan, Ermeson, Red Chamber According to the Google development group, beta version will become 49 today (and dev 50). So the situation you all mentioned won't last long.

6:45 AM, January 28, 2016  
Blogger Duncan McLellan said...

I can see with Sawbuck that Google Update when it's set to only autoupdate Chrome, is still only dishing out Chrome 47:

WARNING 14740 12560 17:01:11-678 0 [01/28/16 17:01:11.709]
[GoogleUpdate:goopdate][14740:12560][BITS download was redirected]
[http://r1---sn-aigllnsd.gvt1.com/edgedl/release2/da0sy2z45to46g6wduiortgcqnsa32lwp26ieujfc94a7suoslwcx5pmeshvpzew7test0j6e3od8rbforsw7g123uqn7k9o99i/47.0.2526.111_chrome_installer.exe.....


So is Chrome 48 only via manual update at this time?

9:19 AM, January 28, 2016  
Blogger Ed Bugliarelli said...

I got Chrome's current update & didn't even know it? On windows Chrome browser 48.0.2564.97... runs fine

8:48 AM, January 29, 2016  
Blogger ticklingthemivories said...

I've been having problems with Chrome ranging from working fine to being totally unresponsive for what seems like a year now ("Establishing secure connection" or something else in the status). This release finally seems to have fixed this. Finally.

Running on Windows 10 64-bit and Windows 8 (ugh - corporate standard)

5:02 PM, January 31, 2016  
Blogger Sean Rivera said...

I'm not certain if Chrome updated to the latest version (48.0.2564.97) last night but when I unlocked my iMac (running Mavericks 10.9.5) this morning, Chrome no longer displays websites correctly. Large black blocks appear in the window. If I move the mouse cursor over them, some will stay and others will disappear and show the webpage underneath. It seems like there's an issue drawing the window. The toolbar, address bar, bookmark bar and window frame all appear to be drawn correctly but the content of the webpage doesn't. This is only happening to the Chrome web browser. My other browsers (Safari / Firefox) seem to be working fine. Despite exiting Chrome and restarting it, the problem persists. Is anyone else having this issue?

11:07 AM, February 02, 2016  
Blogger Karthikeyan Subbiah said...

After updating my chrome browser to v48.0.2564.97, my web page is not displaying the contents any more and when I inspect the console of the browser, it shows below error messages.
Error Messages:
-----------------
Uncaught TypeError: path.createSVGPathSegLinetoAbs is not a function
Uncaught TypeError: svgedit.browser.supportsSelectors is not a function
svgedit.browser.isTouch is not a function
svgedit.browser.isWebkit is not a function

I will really appreciate for any help that will help me to solve the above issues.

11:13 PM, February 02, 2016  
Blogger Nickolas Damofli said...

Web Speech API is messed up (lang var is ignored)

6:50 AM, February 03, 2016  
Blogger Karthikeyan Subbiah said...

Could anybody please let me know how do I resolve this issue posted above on 11:13 PM, February 02, 2016.

12:09 AM, February 04, 2016  
Blogger Eric Ahnell said...

@Karthikeyan Subbiah Are you using the SVGEdit library (which moved to GitHub from Google Code) on your web site? Upgrading to 2.8.1 should fix things.

3:56 AM, February 04, 2016  
Blogger Sean Rivera said...

Chrome just updated itself again to version 48.0.2564.103 and it seems to have fixed my issue.

7:00 AM, February 04, 2016  
Blogger Karthikeyan Subbiah said...

@Eric Ahnell, Thanks a lot for your response. I will try to upgrade it as you suggested.

1:47 AM, February 08, 2016  
Blogger Karthikeyan Subbiah said...

@Eric Ahnell, After upgrading svg edit library from 2.6 to 2.8.1, still I am getting below errors. Any idea on how to resolve these issues?
Uncaught TypeError: path.createSVGPathSegLinetoAbs is not a function
Uncaught TypeError: svgedit.browser.supportsSelectors is not a function
Uncaught TypeError: svgedit.browser.isTouch is not a function
Uncaught TypeError: editor.putLocale is not a function

5:48 AM, February 09, 2016  
Blogger Eric Ahnell said...

The first two errors can be fixed by adding a polyfill from GitHub. Instructions here: SVG selectors removal

6:03 AM, February 09, 2016  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home