Tuesday, August 6, 2019

Stable Channel Update for Desktop

The stable channel has been updated to 76.0.3809.100 for Windows, Mac, and Linux, which will roll out over the coming days/weeks.

Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.

This update includes 4 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.

[$5000][983867] High CVE-2019-5868: Use-after-free in PDFium ExecuteFieldAction. Reported by banananapenguin on 2019-07-14
[$TBD][984344] Medium CVE-2019-5867: Out-of-bounds read in V8. Reported by Lucas Pinheiro, Microsoft Browser Vulnerability Research on 2019-07-15
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

As usual, our ongoing internal security work was responsible for a wide range of fixes:
[991355] Various fixes from internal audits, fuzzing and other initiatives

Many of our security bugs are detected using AddressSanitizerMemorySanitizerUndefinedBehaviorSanitizerControl Flow IntegritylibFuzzer, or AFL.

A list of all 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.

Abdul Syed
Google Chrome

Labels: ,


Blogger Rad P. said...

I think this update introduced a serious annoyance. I work on 2 Windows desktops (the ones you can swap with CTRL+Win key+arrow left/right). I always used to have Chrome browser on Desktop 1, Slack and Excel on Desktop 2. Whenever I had links from Slack, they would open in the default Chrome window - meaning I click on a link in Slack (Desktop 2) and the link opens in Chrome (Desktop 1). Now, after the update, all links from Slack and other programs open a new Chrome window on the desktop they are clicked on - meaning, all my links from Slack, Excel and anything on Desktop 2, open a new Chrome window on Desktop 2, instead of opening a new tab in Chrome on Desktop 1.

2:55 AM, August 08, 2019  
Blogger g said...

When will the webdriver for this version be released ?

6:26 AM, August 08, 2019  
Blogger Unknown said...

- I hade this error on my app that i haven't before the update.
Uncaught TypeError: loading.show is not a function
at HTMLImageElement.onclick
-I already tested on several computers before and after the chrome update.

6:42 AM, August 08, 2019  
Blogger Barakat Al-Hamzi said...

the problem of chrome now it take from ram
i dont know why like this
the others not like it why >?

3:04 PM, August 08, 2019  
Blogger Web Design Company In Pune said...

I am not able to https in the url. Is it hidden in new update or have any issue?

8:25 PM, August 09, 2019  
Blogger mylifeonablog said...

https:// is just getting hidden, the address is still captured as required

7:13 AM, August 10, 2019  
Blogger raphaelbm said...

re: mylifeonablog said...
https:// is just getting hidden, the address is still captured as required

You can click on the address bar to show the full URL including HTTPS: or whatever.
Also, on Windows press function key F6 to see the full URL.
Hope that helps

8:43 AM, August 10, 2019  
Blogger Metablocks said...

My extensions are NO longer showing next to the address, MAJOR problem.

3:52 PM, August 10, 2019  
Blogger Unknown said...

My Sites are Opening Untied Pages When Clicking on Links Now? How do I fix this?

1:09 AM, August 12, 2019  
Blogger A said...

javascript:__doPostBack broken. Meaning ASP.NET forms are now broken. Probably millions of websites affected.

3:03 AM, August 12, 2019  
Blogger A said...

"My Sites are Opening Untied Pages When Clicking on Links Now? How do I fix this?" this is same as javascript:__doPostBack not working. Not happening on all pages, just some. Still investigating...

3:06 AM, August 12, 2019  
Blogger A said...

For anyone interested: Previously links that had href="javascript:..." and also had target="_blank" still executed the javascript. In this latest update it does not execute the javascript, instead it opens a new tab. Simply removing the target from the link fixes this issue.

3:22 AM, August 12, 2019  
Blogger Xyloguy said...

Updating to this version using MacOS introduced the "Printer Features" option when printing. However Chrome is not honoring the PPD options that I select when using this new feature. Essentially advance printing is now broken in Chrome.

11:14 AM, August 20, 2019  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home