Chrome Releases

Release updates from the Chrome team

Stable Channel Update for Desktop

Tuesday, January 29, 2019
Share on Google+ Share on Twitter Share on Facebook
Google
Labels: Desktop Update , Stable updates

18 comments :

fracTure said...
This comment has been removed by the author.
4:23 PM, January 29, 2019
Markus Thiel said...

We have major issues when updating to chrome 72...
Images are not sized properly and performance are super bad on initial load?

It feels like rendering stopps untill all images are loaded?

12:11 AM, January 30, 2019
Unknown said...

F12 doesn't open the dev tools anymore :|

2:03 AM, January 30, 2019
Dr-Kermit said...

THis version is very buggy, unstable and slow.
takes 2-3 seconds to activate adressbar when clicked upon, eats 1000mb of ram, with no tabs open and no extension loaded.

Literaly not working.

/Kenneth

6:21 AM, January 30, 2019
Septua Genarian said...

My AV, Comodo, tells me that Chrome.exe is trying to change me settings. I have declined, twice. I wish I knew what was going on. Just trust Google Chrome???

Charles Levy Oakland CA

8:02 AM, January 30, 2019
Unknown said...

We are having Major issue with RTCPeerConnectionIceEvent since browsers got updated to Chrome version 72.0.3626.81, seems not to be compatible. With With chrome prior version 71.0.3578.98 it worked fine.

9:03 AM, January 30, 2019
fracTure said...
This comment has been removed by the author.
12:02 PM, January 30, 2019
Unknown said...

updating to this 72 version then got black screen when streaming video on youtube.com

chrome://gpu
Log Messages
GpuProcessHostUIShim:
GpuProcessHostUIShim:
[4668:1384:0131/113912.602:ERROR:gles2_cmd_decoder.cc(15917)] : Context lost because SwapBuffers failed.
[4668:1384:0131/113912.602:ERROR:gles2_cmd_decoder.cc(5792)] : Error: 5 for Command kPostSubBufferCHROMIUM
[4668:1384:0131/113912.602:ERROR:gpu_channel_manager.cc(218)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.

===========================================================================
Processor AMD A10-9600P
GPU0 VENDOR = 0x1002, DEVICE= 0x9874 *ACTIVE*
GPU1 VENDOR = 0x1002, DEVICE= 0x6900

8:47 PM, January 30, 2019
یو پی اس said...

Aw, this was an extremely good post.
صبا باتری

12:34 AM, January 31, 2019
Sunila said...

Crystal report and chrome print preview is not compatible anymore. Page unresponsive message appears in print preview of crystal report.

2:36 AM, January 31, 2019
brocolliInDB said...

===================================
SVG ISSUE!!!!!!
===================================
I'm not sure if this has been done on purpose or not.
However the fact is that utf-8 encoded svg is not shown on browser since chrome 72 version updated on windows10, ubuntu 18.04, Mac.

I have already tested this for those 3 OS systems and 71 version chrome as well.

If there is any way to use utf-8 format. plz let me know.
If there is any reason for this issue. plz let me know as well.

There is an example below: same svg
from http://tutorials.jenkov.com/svg/simple-svg-example.html

[UTF-8]
data:image/svg+xml;utf-8,

[base64]
data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIj4gPHJlY3QgeD0iMTAiIHk9IjEwIiBoZWlnaHQ9IjEwMCIgd2lkdGg9IjEwMCIgc3R5bGU9InN0cm9rZTojZmYwMDAwOyBmaWxsOiAjMDAwMGZmIi8+IDwvc3ZnPg==

9:18 AM, January 31, 2019
Unknown said...
This comment has been removed by the author.
11:53 AM, February 01, 2019
Unknown said...

Can confirm the SVG UTF-8 issue.
Found more information as to why they may have removed it here: https://stackoverflow.com/questions/54453987/did-chrome-72-break-dataimage-svgxmlutf8-for-css-background-svgs

1:09 PM, February 01, 2019
Manish said...

Clear browsing data hangs with latest version.

Steps
1) Browser through the day or couple of days
2) Clear browsing data and chrome browser hangs.
3) Restart chrome and then clear browsing works.

Google Chrome 72.0.3626.81 (Official Build) (64-bit)
Revision ac8b982e05014492d1bd7d317628a4f22a97ffa0-refs/branch-heads/3626@{#796}
OS Mac OS X
JavaScript V8 7.2.502.24
Flash 32.0.0.114 /Users/mjhanji/Library/Application Support/Google/Chrome/PepperFlash/32.0.0.114/PepperFlashPlayer.plugin
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.81 Safari/537.36

1:13 AM, February 02, 2019
mikeoke said...

if you Uncheck "Use hardware acceleration when available" and have your browser in Fullscreen mode there is a lot of screen lag when you move other windows around.
Something like following screenshot
https://i.stack.imgur.com/BJGBH.png

When you enable hardware acceleration or do not have chrome in Fullscreen mode there is nog more screen lag.

3:59 AM, February 02, 2019
SerapH~~ said...

new version cost much more cpu!!!!

12:17 AM, February 03, 2019
RoshJ said...

Is there any known fix to the SVG issue. This has completely destroyed the formatting of SVG images in our navigation and caused the application to become nearly unusable.

There was a solution around # characters not encoding correctly in this response from Robert Longson
https://stackoverflow.com/questions/30676125/svg-as-data-uri-triggers-xml-parsing-error-in-firefox/30676203#30676203

However, this doesn't seem to be working in my case. Any ideas on how to work around this. Would be awesome if Google could publish some migration solutions when releasing a breaking change such as this.

11:00 PM, February 03, 2019
Dan said...

This version is bringing my computer to a crawl, and I'm having the same issue as "mikeoke" earlier in the comments section. Would like a fix to this version ASAP.

9:01 AM, February 05, 2019

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


  •     2019
    • Feb
    • Jan
  •     2018
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • 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