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.

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. The total value of additional rewards and their recipients will be updated here when all reports have gone through the reward panel.

As usual, our ongoing internal security work was responsible for a wide range of fixes:

[463349] CVE-2015-1231: Various fixes from internal audits, fuzzing and other initiatives.

Multiple vulnerabilities in V8 fixed at the tip of the 4.1 branch (currently 4.1.0.21).

Everything is good, but again YouTube videos in 1080p are a bit laggy for me, and on YouTube the main search gap, when you write some text here, the text strange goes up and it is ugly. That problem is with writing to the upper gap in Chrome, when you are searching web pages, and when it turns blue, it is not symmetrical. But very good update at all. Bye.

We have also an issue with Chrome v41 and NTLM-Authentication against our Squid-Proxyserver. With V40 everything is good, with v41 Chrome can not authenticate himself / the logged on user against the Squid-Proxy via NTLM.

We also had a similar issue this morning. NTLM authentication was not working when accessing HTTPS sites. We are using McAfee Web Gateway. The issue turned out to be with chunked encoding. Once we enabled the browser to negotiate chunked encoding HTTPS sites started working. Hope this helps.

Sorry, my mistake. On YouTube the main search gap, when you write some text here, the text strange goes up and it is ugly. That problem is with writing to the upper gap in Chrome too, when you are searching web pages, and when it turns blue, it is not symmetrical.

We have also an issue with Chrome v41 and NTLM-Authentication against our Squid-Proxyserver. With V40 everything is good, with v41 Chrome can not authenticate himself / the logged on user against the Squid-Proxy via NTLM.

We have also an issue with Chrome v41 and NTLM-Authentication against our Squid-Proxyserver. With V40 everything is good, with v41 Chrome can not authenticate himself / the logged on user against the Squid-Proxy via NTLM.

A question about "affirmatively secure:" how will this actually appear in my browser? I'm currently using Chrome 41 to access one of my SHA-1/2017-expiration sites, and apart from "https:" appearing in gray like a non-HTTPS site, there's no indication that the site is insecure. In other words, how has the behavior changed since Chrome 40? How is/was it supposed to change?

I have Chrome distributed to 3,500 PCs in an enterprise environment with auto update enabled. Since the update from version 40 to 41 we are having problems where Chrome 41 will crash immediately at start up, on both Windows XP and 7. Process monitor does not reveal anything out of the ordinary. There are no Chrome crash logs created. Has anyone else experienced this?

Dito what Erwin Zengerink said. I'm also having problems with Chrome crashing all of the sudden on startup. I have around 650 pc, and I'm starting to get multiple reports of this. We use redirected directories and roaming profiles. If I delete the "Local State" file in the profile directory I can get it to start again, but only once.

The new update has some issues with font .. the size of the font has become smaller .. specially on Google Spreadsheets, which I use most of the time .. I am not sure why there is a need to finger in things which are working perfectly ..

I have a problem that when going to Facebook the Shockwave Flash plugin crashes and the page becomes unresponsive. I have tried recommended solutions on Google search and nothing is working (only one SW Flash plugin showing). I never had this problem before this latest update. Running Windows 7 Home Edition on a 64 bit machine. Is SW Flash player so built into this update that it does not show up as a plugin?

MASSIVE problems with Chrome 41 on Windows 7 64bit. It is practically unusable, It lags and crashes all the time, takes 3-4 seconds to switch tabs, the transparency doesn't work in the title bar, and YouTube videos play like crap. What is going on google? this thing goes through around 3 stages before it is released, and you never catch any of these problems?

We use roaming profiles and redirect google chrome folders with GPO. Everything worked in previous versions. With version 41 Chrome does not start. If I delete the users chrome data catalog in %appdata% it will open once, the folders will be recreated but if the user closes Chrome it will not open the next time again.

“Our environment was working perfectly until Chrome 41, as users upgraded we found they couldn't open their browser at all. After much troubleshooting we found that it was all down to how we had specified out UserDataDir - we previously had '{$roaming_app_data}\Google\Chrome\', which worked fine. Note that we set this using Chrome group policy.

As of Chrome 41, the trailing backslash causes the above issue. Removing the backslash fixes the issue.”

Visual effects in Windows settings (performance options) changes the blurry smoothing UI font in Chrome. Uncheck the option "Smooth edges of screen fonts" BUT then the fonts in Outlook or other apps are awful, even in web pages... so I hope there will be some other correction for this bug.

Disabling DirectWrite helps a bit, but the font still doesn't look like it used to; it's still off.

I'm just glad I don't use Chrome for anything except video (twitch/youtube 60fps), so I don't really care that much about it to the point where I'd downgrade, otherwise I would go back to v40 as this is unacceptable.

The Chrome UI and webpages no longer respond to mouse events properly (especially mouseovers and dragging) when using Chrome 41 for Linux (Xubuntu 14.10) in VirtualBox for Windows 7. Version 40 worked fine.

A workaround seems to be disabling the mouse integration, but that needs to be done every time I boot up the virtual PC, so it is annoying. No other program seems to be suffering from this issue.