After the 66.0.3359.117 update, my javascript code is running 40% slower (2000 trials, 50ms average is now 70ms). It's running the same in Firefox. Yikes.
On Ubuntu 16.04, just upgraded to 66.0.3359.117. When I close the browser, I seem to lose all my cookies. I have to sign back into gmail, and everything else.
@Rob Sutcliffe - I disabled all my extensions in chrome://extensions/ and it's back to normal now. Haven't taken the time to re-enable them and test which one is the problem. Extensions I had enabled: AppsScript Color Google Docs Offline Grammarly for Chrome Stylebot
Chrome Apps: Caret Chrome RDP Chrome Remote Desktop Docs Google Hangouts Google Play Music Postman Secure Shell App Sheets Slides
@Unknown @koushikshaha You most likely are running a buggy graphics driver version that Google needs to put on the Hardware Acceleration blacklist. A bug report with the symptom (black boxes), the operating system version, the graphics card maker's name, and the graphics driver version would help immensely in limiting the scope of the problem, so future users do not have to deal with it.
But this did not ever happen with any of the previous versions of Chrome. Also does this have any effect on my internet download speed? Any help would be greatly appreciated!
@koushiksaha Both good questions. Odds are, since the Chrome update happened around the same time as Microsoft Patch Tuesday (if you're running Windows), a graphics driver update was included with the rest of the patches - which unfortunately does not play nice with Google Chrome's hardware acceleration implementation. Since this is confined to the interaction between your operating system and graphics card, it should not affect networking in any way, speed included. Download speeds (and upload speeds) should not change before or after any fix for the black boxes issue for this reason. However, Google can't fix issues they don't know about - hence why reporting them at crbug.com is so important to getting them triaged and fixed.
Follow
11 comments :
After the 66.0.3359.117 update, my javascript code is running 40% slower (2000 trials, 50ms average is now 70ms). It's running the same in Firefox. Yikes.
On Ubuntu 16.04, just upgraded to 66.0.3359.117.
When I close the browser, I seem to lose all my cookies. I have to sign back into gmail, and everything else.
When I try to update the "Origin Trials" component, it's given as "status-update error"
I'm also loosing all cookies when closing the browser. As are others in our team. Windows 1703 - chrome 66.0.3359.117
@Rob Sutcliffe - I disabled all my extensions in chrome://extensions/ and it's back to normal now. Haven't taken the time to re-enable them and test which one is the problem.
Extensions I had enabled:
AppsScript Color
Google Docs Offline
Grammarly for Chrome
Stylebot
Chrome Apps:
Caret
Chrome RDP
Chrome Remote Desktop
Docs
Google Hangouts
Google Play Music
Postman
Secure Shell App
Sheets
Slides
This update made appear random black boxes in certain pages, on Chrome 65 is all good. Deactivating HW accel seems to solve this problem.
Random black boxes appearing on the screen ever since I updated to Chrome Version 66.0.3359.117. Extremely irritating.
@Unknown @koushikshaha You most likely are running a buggy graphics driver version that Google needs to put on the Hardware Acceleration blacklist. A bug report with the symptom (black boxes), the operating system version, the graphics card maker's name, and the graphics driver version would help immensely in limiting the scope of the problem, so future users do not have to deal with it.
But this did not ever happen with any of the previous versions of Chrome. Also does this have any effect on my internet download speed? Any help would be greatly appreciated!
@koushiksaha Both good questions. Odds are, since the Chrome update happened around the same time as Microsoft Patch Tuesday (if you're running Windows), a graphics driver update was included with the rest of the patches - which unfortunately does not play nice with Google Chrome's hardware acceleration implementation. Since this is confined to the interaction between your operating system and graphics card, it should not affect networking in any way, speed included. Download speeds (and upload speeds) should not change before or after any fix for the black boxes issue for this reason. However, Google can't fix issues they don't know about - hence why reporting them at crbug.com is so important to getting them triaged and fixed.
Post a Comment