Chrome Releases

Release updates from the Chrome team

Stable Channel Update for Desktop

Thursday, December 1, 2016
Share on Google+ Share on Twitter Share on Facebook
Google
Labels: Stable updates

29 comments :

Harry Elston said...

This update completely crashes on my Windows 7 machine. Here is the error information:

Problem Event Name: APPCRASH
Application Name: chrome.exe
Application Version: 55.0.2883.75
Application Timestamp: 583f4d64
Fault Module Name: chrome_elf.dll
Fault Module Version: 55.0.2883.75
Fault Module Timestamp: 583f3644
Exception Code: c0000005
Exception Offset: 0000000000027d5c
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: d8f9
Additional Information 2: d8f9a73772ae5e57b8b813b4b4e958dd
Additional Information 3: 5d1b
Additional Information 4: 5d1b9d9d5d0c7db679464094e2a5e3af

8:05 PM, December 01, 2016
Sodasudaso said...

Great, now Chrome hangs for every ten seconds.
I'll rather not have the memory-saving gimmicks...

8:37 PM, December 01, 2016
Yellowstone said...
This comment has been removed by the author.
9:13 PM, December 01, 2016
Yellowstone said...

Does Chrome 55.0 support CFG (Control Flow Guard) yet?
When I updated the 55.0, Control Flow Guard (CFG) was disabled.
System requirements: Windows 10 64-bit version
Chrome version: 55.0.2883.75 m (64 bit)

Note: Translated into Google Translator (Korean language-> English)
Please acknowledge this... -_- ;;

9:15 PM, December 01, 2016
王宁 said...
This comment has been removed by the author.
1:43 AM, December 02, 2016
Ning Wang said...

I heard that Chrome 55 reduces up to 50% memory usage, is that true?

1:50 AM, December 02, 2016
Urtynas said...

Is there any way to un-install the new update on mac?

3:02 AM, December 02, 2016
Harry Elston said...

Uninstall and reinstall did not work. I need this for my company. Is there any way I can get the old version back. It's completely hosed on my system. Here is the crash report again:

Problem Event Name: APPCRASH
Application Name: chrome.exe
Application Version: 55.0.2883.75
Application Timestamp: 583f4d64
Fault Module Name: chrome_elf.dll
Fault Module Version: 55.0.2883.75
Fault Module Timestamp: 583f3644
Exception Code: c0000005
Exception Offset: 0000000000027d5c
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: d8f9
Additional Information 2: d8f9a73772ae5e57b8b813b4b4e958dd
Additional Information 3: 5d1b
Additional Information 4: 5d1b9d9d5d0c7db679464094e2a5e3af

6:20 AM, December 02, 2016
Louis said...

Hello,

W7/32,Omega drivers (14.12)
chrome://gpu/

Log Messages
[9196:8844:1202/144651:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 345
[9196:8844:1202/152758:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 345
[9196:8844:1202/152759:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 345
[9196:8844:1202/152909:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 345
[9196:8844:1202/153320:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 345
[9196:8844:1202/153320:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 345
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.



6:40 AM, December 02, 2016
Gordon Hawley said...

Great update. No problems here on an outdated work computer running Windows 7.

6:51 AM, December 02, 2016
Very Anonymous User said...
This comment has been removed by the author.
7:17 AM, December 02, 2016
Anonymous said...

No yum package :(

7:22 AM, December 02, 2016
sadi porter said...

I thought v55 was supposed to reduce memory by up to 50%? I don't see any change in memory consumption.

8:02 AM, December 02, 2016
Krishna Govind said...

Harry Elston@, could you please report a bug under crbug.com for the crash you're seeing with all details and repro steps. Thank you.

8:53 AM, December 02, 2016
Saso Badovinac said...

It seems like that with this update chrome is not catching the middle mouse button double click event anymore? Can someone confirm? Hopefully it will get fixed...

9:42 AM, December 02, 2016
Unknown said...

NEWBIE , but chrome, has been crashing , not installing properly, and this new version stable win 10 64 bit, 55.0.2883.75m has been glitching, flashing, slow, lots of issues.

12:29 PM, December 02, 2016
Dan Weiser said...

I think I will remove Google Chrome via Paid Revo Uninstaller and use Mozilla Firefox and or Internet Explorer until the glitches are resolved with Google Chrome. Mozilla Firefox had a critical patch fixed recently so it should be okay for the time being. I currently use Windows 7 64 bit with EMET 5.5. I do not like the Micorosft is ending support for EMET in July 2018. I think support should be extended until at least January 2020 which will conicide with the end of support for Windows 7 and then Microsoft can fully fold EMET into Windows 10. I do not like Windows 10 that forces you to give basic telemetry information unless you are an enterprise edition. Microsoft is trying to force that on Windows 7 and 8.1 users as well unless they are in Group B and now only updating the security patches each month. I guess eventually I may have to go into Group A and except everything from Microsoft but I will hold out as long as I can.

2:36 PM, December 02, 2016
Harry Elston said...

@Krishna Govind - I am working with folks at crbug.com now. Thanks for the help.

6:09 AM, December 03, 2016
Louis said...

Ms Govind,I have these log messages wit two tabs opened:
- https://googlechromereleases.blogspot.fr/2016/12/stable-channel-update-for-desktop.html
- chrome://gpu/

Log Messages
[1792:8208:1204/080433:ERROR:gles2_cmd_decoder.cc(16349)] : [.DisplayCompositor-0838C2A0]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1792:8208:1204/080433:ERROR:gles2_cmd_decoder.cc(9063)] : [.DisplayCompositor-0838C2A0]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1792:8208:1204/080433:ERROR:gles2_cmd_decoder.cc(16349)] : [.DisplayCompositor-0838C2A0]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1792:8208:1204/080433:ERROR:gles2_cmd_decoder.cc(9063)] : [.DisplayCompositor-0838C2A0]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1792:8208:1204/080433:ERROR:gles2_cmd_decoder.cc(16349)] : [.DisplayCompositor-0838C2A0]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1792:8208:1204/080433:ERROR:gles2_cmd_decoder.cc(9063)] : [.DisplayCompositor-0838C2A0]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.

11:09 PM, December 03, 2016
Unknown said...

55.0.2883.75 its teribble, slow, freezes

10:18 AM, December 04, 2016
Phil in UK said...

After having problems with Chrome crashing I was delighted to notice that it did an update to Version 55.0.2883.75 m. However, this seems a backward step as Version 55.0.2883.75 m closes itself after approximately 5 seconds. No error messages are presented it just closes.

I have ALL of my browsing through Chrome - highly disappointed that a buggy version of Chrome has been upgraded to an even more buggy and unusable version.

What is happening to Google - did not expect this "experience"...

2:31 AM, December 05, 2016
Cory Serratore said...

I'm seeing significant CSS regressions with this update. Anyone else?

6:43 AM, December 05, 2016
Krishna Govind said...

@Louis, @Phil in UK and @Cory Serratore, could you please report a bug under crbug.com for the crash/issue you're seeing with all details and repro steps. Thank you.

10:40 AM, December 05, 2016
Ovidiu Petruescu said...

Huge defect with multiple sites being broken:

https://bugs.chromium.org/p/chromium/issues/detail?id=671303

12:59 PM, December 05, 2016
Kevin Morris said...

Windows 7 64bit
Chrome 55.0.2883.75 m randomly does these things
- crashes completely (actually closes)
- locks up but will close by hitting X
- pauses for several seconds

[] PLEASE FIX SOON []

2:42 PM, December 05, 2016
Gyorgy Peremi said...

55.0.2883.75 m (64-bit) has no Character Encoding menu, deleted fallback enconding fonts settings and reseted codepage settings to automated. It's a HUGE problem as it still NOT WORKS WELL and confuse ISO-8859-2 (Latin2) with windows-1252. So we miss 2 letters from our ABC.

Turn back the menu, some not so old systems still needs that.

1:06 AM, December 06, 2016
Manfred Rotgers said...

What happend to the 'add a person'/ 'switch accounts' option in the top of the browser screen?
the selection window has disappeared/ I have so many accounts they do not fit in the dropdown list, and there is no scroll option there for switching accounts.

6:20 AM, December 07, 2016
Alex Garfield said...

I am writing to suggest everyone consider moving back to Mozilla Firefox, Internet Explorer or Microsoft Edge because clearly Google Chrome 55 should still be in the beta testing phase and is not a finished product. These other browsers allow you to migrate your settings into them to allow for an easier time to switch browsers when needed.

7:22 AM, December 07, 2016
Jit Kapur said...

ON ASUS windows PC the Chrome browser 55.0.2883.75 m (64-bit) is crashing ever few seconds. If I do get a web page, it freezes after a few seconds. I reload the page and freezes again randomly. Please publish how to install an older version of Chrome while a solution is found

Thanks

6:18 PM, December 08, 2016

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


  •     2018
    • 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