There is a bug in the latest update that causes the browser to crash. Various oddball url's will crash chrome http://b/%00 will crash chrome - this is being reported all over and there is an interesting back and forth by Chrome coders here - https://code.google.com/p/chromium/issues/detail?id=533361#c3
The stable channel has been updated to 45.0.2454.101 for Windows, Mac, and Linux. The following bugs from external security researchers were fixed in this release: [$TBD][530301] High CVE-2015-1303: Cross-origin bypass in DOM. Credit to Mariusz Mlynski. [$TBD][531891] High CVE-2015-1304: Cross-origin bypass in V8. Credit to Mariusz Mlynski.
FYI. Google Chrome Portable 45.0.2454.101 Stable (web browser) Released for the PA Platform, courtesy of PortableApps.com.
Google Chrome 46.0.2490.71 released today. http://googlechromereleases.blogspot.fr/2015/10/stable-channel-update.html
Second attempt I got ~ Version 46.0.2490.71 m (64-bit) First attempt I got ~ I didn't download Chrome again, I just closed it, opened it and tried to update again. Chrome is weird.
Had the same error here as well, I just hit F5 to refresh the about page & it then installed the update ok.
First try compression failure here as well. Second try was successful. Is there a slight change in color to the Chrome icon with this release or I am just losing my mind?
@Page42 Up until 10 minutes ago, I was certain I had lost my mind as well. I searched all over the web, including Chromium sources and detailed release notes, etc. and found nothing. However... the new icon has gone "flatter", I suppose. Left is from 46.0.2490.71, while Right is from 45.0.2454.101.
I noticed my chrome tray icon looked different soon after the last update. It caught my eye because of a change of color or brightness.
FYI. Google Chrome Portable 46.0.2490.71 Stable (web browser) Released for the PA Platform, courtesy of PortableApps.com.
Chrome has just been updated to include Flash Player 19.0.0.226, with Chrome version 46.0.2490.71. EDIT: So it appears as though they pushed Flash update within same Chrome version. EDIT2: What I am finding to be odd, though, is that Chrome is now starting to execute Flash from User directory: C:\Users\{user-name}\AppData\Local\Google\Chrome\User Data\PepperFlash\19.0.0.226\pepflashplayer.dll Normally it would copy that Flash DLL to it's typical Program Files location and execute from there. So something is different here with this update.
@Page42 On my system, it updated Flash during system boot. So I was alerted to the Flash DLL (pepflashplayer.dll) trying to execute while Windows was still booting. EDIT: If I had to guess, I would guess that one of the two scheduled tasks for GoogleUpdate is likely what brought in the Flash update for Chrome. You could try manually going into Task Scheduler and running those tasks. However, this update appears to be coming out fast as Adobe has updated all of their usual download pages already which is unusually quick for Adobe.