Tuesday, September 9, 2014

Stable Channel Update

The stable channel has been updated to 37.0.2062.120 for Windows, Mac and Linux.

This release contains an update for Adobe Flash as well as a number of other fixes.  A full list of changes is available in the log.

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 either contributed by external researchers or particularly interesting. Please see the Chromium security page for more information.

[$2000][401362] High CVE-2014-3178: Use-after-free in rendering. Credit to miaubiz.

As usual, our ongoing internal security work responsible for a wide range of fixes:
[411014] CVE-2014-3179: Various fixes from internal audits, fuzzing and other initiatives.

Many of the above bugs were detected using AddressSanitizer.

Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Alex Mineer
Google Chrome



Blogger Ray890 said...

It'd be a little helpful if at least a little more information on what's new in the update was provided, instead of referring us to the "developer log". (where everything's all explained in confusing programming speak)

10:56 AM, September 09, 2014  
Blogger Moo Scree said...

64-bit "unknown-m" fixed. But now that damn "Disable developer mode extensions" message is back.

11:39 AM, September 09, 2014  
Blogger Athanasius said...

"Shockwave Flash has crashed" all over my Facebook home page using Version 37.0.2062.120 (64-bit) on Debian Wheezy Linux.

3:29 PM, September 09, 2014  
Blogger Unknown said...

It would be very helpful to add (32-bit) or (64-bit) to the version info on the "About Google Chrome" tab.

Right now it's not all that easy to tell which I'm running. Did I install 32 or 64 or this particular computer? Does Chrome automatically update from 32 to 64 if it's a 64-bit system? Chrome also seems to leave 32 bit remnants in x86 folder. Am I using 64-bit sometimes and 32-bit sometimes depending on what shortcut I click?

Having to view properties on whatever shortcut to verify the directory it points to is a pain when it could be easily added to the About tab.

5:00 PM, September 09, 2014  
Blogger A.J. Zuniga said...

Getting a ton of "Shockwave Flash has crashed" as well.

Distributor ID: Debian
Description: Debian GNU/Linux 7.6 (wheezy)
Release: 7.6
Codename: wheezy

Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux

Google Chrome 37.0.2062.120


I completely purged Chrome. I completely purged the Flash plugin. I also noticed I had Gnash installed and purged that as well.

I then reinstalled Chrome and I am still getting the same error.

6:13 PM, September 09, 2014  
Anonymous Anonymous said...

Fonts are still tiny.
Google Chrome is unusable.

6:56 PM, September 09, 2014  
Blogger ieti said...

Flash crashes with latest Chrome of Debian Wheezy:

[36:36:0910/081252:ERROR:ppapi_thread.cc(279)] Failed to load Pepper module from /opt/google/chrome/PepperFlash/libpepflashplayer.so (error: /opt/google/chrome/PepperFlash/libpepflashplayer.so: cannot open shared object file: Operation not permitted)
[26:26:0910/081252:ERROR:webplugin_delegate_proxy.cc(318)] Plug-in crashed on start
ieti@loki:~$ ldd /opt/google/chrome/PepperFlash/libpepflashplayer.so
/opt/google/chrome/PepperFlash/libpepflashplayer.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/google/chrome/PepperFlash/libpepflashplayer.so)
linux-vdso.so.1 => (0x00007fff82cc9000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fe595125000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fe594f1d000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fe594c15000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fe594993000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fe59477d000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fe594560000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe5941d5000)
/lib64/ld-linux-x86-64.so.2 (0x00007fe596662000)

Seems the plugin wants GLIBC 2.14. Wheezy comes with 2.13

10:16 PM, September 09, 2014  
Blogger l33tf0rg said...

@ieti: you can try thisworkaround: "download stable chrome deb package from website, use alien on it to convert it to tar, extract files, copy and replace libpepflashplayer.so from the stable build... restart chrome".

12:29 AM, September 10, 2014  
Blogger raphaelbm said...

Now we have Chrome version
37.0.2062.120 09.09.2014
Very recently we had
37.0.2062.103 03.09.2014 36.60MB
37.0.2062.102 29.08.2014 36.60MB
36.0.1985.143 14.08.2014 36.60MB
36.0.1985.125 17.07.2014 36.60MB

The speed of the new STABLE releases is unbelievable and getting faster. Can anyone tell me how this can be. Did someone just fire off releases for the fun of it. Why this fast re-release cycle? Raphael

2:29 AM, September 10, 2014  
Blogger Klaus Hählen said...

@l33tf0rg: This workaround worked for me, I was using the previous stable package from 19.08.2014, when I installed initially google-chrome on a fresh Debian installation. The crush seems to be a regression...
Debian Wheezy with completed apt-get update && apt-get dist-upgrade.


5:18 AM, September 10, 2014  
Blogger ieti said...

@l33tf0rg this works yep. :)

Sadly package downloaded from site is latest version now too. I found an mirror (thanks to stackoverflow) with following:


Got older libpepflashplayer.so from google-chrome-stable_37.0.2062.94-1_amd64.deb

When they fix it will return latest version.

11:07 AM, September 10, 2014  
Blogger Tk421 said...

@i33tf0rg, thanks for the solution

@ieti, thanks for the location of older releases

These two steps worked for me

12:45 AM, September 11, 2014  

I am Brazilian and I live in São Paulo.
I'm having trouble with the "Shock Wave".
I use Debian GNU / Linux 7.6 (wheezy) and am having trouble accessing many pages. I've tried all the solutions but I could not until now.

Eu sou brasileiro e moro em São Paulo.
Eu estou com problemas com o "Shock Wave".
Eu uso o Debian GNU/Linux 7.6 (wheezy) e estou com problemas para acessar muitas páginas. Já tentei todas as soluções mas não consegui até agora.

7:43 AM, September 11, 2014  
Blogger felipe vieira borba said...

Its impossible to use chrome now, since the update i have "Shockwave Flash has crashed" all time. some solution? i have tried to downgrade the libflash but with no sucess.

11:05 AM, September 11, 2014  
Blogger David Grant said...

Same problem here. On Debian Wheezy 64-bit. "Shockwave Flash has crashed"

11:20 AM, September 11, 2014  
Blogger Klaus Hählen said...

@David Grant: Check @ieti from 11:07 AM, September 10, 2014. This solution works fine, even if it's stupid work for stupid error in stupid flash...


12:21 PM, September 11, 2014  
Blogger David Grant said...

Can someone please save us all some time and post a URL to the old .deb? Thanks.

12:42 PM, September 11, 2014  
Blogger Klaus Hählen said...


Take the 2nd entry.


12:46 PM, September 11, 2014  
Blogger David Grant said...

Ouch, you got me Klaus. I've sent LMGTFY links to people before but this is the first time I've received one. I thought I was a google master but had no idea about the "inurl:" parameter. Thanks.

12:51 PM, September 11, 2014  
Blogger David Grant said...

For me, the first link is the one you want.

12:53 PM, September 11, 2014  
Blogger Klaus Hählen said...

@David: You're right, the first one was the one you need, I didn't check it anymore :P


1:00 PM, September 11, 2014  
Blogger raphaelbm said...

Previous versions of Google Chrome are being assembled at DownloadASTRO.com
This is a Cyprus based web site. see http://google_chrome.en.downloadastro.com/old_versions/

I am sure that Google and Chrome won't like this. I have found this a good resource to roll back to the previous version when required. Raphael

4:56 PM, September 11, 2014  
Blogger George Halkias said...

Hi to All
here it is a working easy solution.

do the following.

#cd /var/cache/apt/archives/

#ls -l google-chrome-stable*
-rw-r--r-- 1 root root 48424346 Aug 12 22:18 google-chrome-stable_36.0.1985.143-1_amd64.deb
-rw-r--r-- 1 root root 49345156 Sep 9 19:32 google-chrome-stable_37.0.2062.120-1_amd64.deb

select an older version.

#dpkg -i google-chrome-stable_36.0.1985.143-1_amd64.deb

that's it!!!

12:09 AM, September 12, 2014  
Blogger Unknown said...

can no longer run shockwave without following warning:
Shockwave Flash has crashed.

Debian Wheezy
Chrome Version 37.0.2062.120 (64-bit)

7:48 AM, September 12, 2014  
Blogger P. said...

Sorr for my english.
It is not necessary to install all chrome 36. You have to just extract from .deb or .rpm package a file: /opt/google/chrome/PepperFlash/libpepflashplayer.so and replace existing plugin with extracted from package in /opt/google/chrome/PepperFlash/
It downgrade your flash player but not whole browser. It works for me.

greetings P.

9:59 PM, September 12, 2014  
Blogger irfan a.r said...

Online Easy Jobs from home with data entry, copy pasting, facebook jobs

8:30 AM, September 13, 2014  
Blogger kamaferro said...

the issue of error 12 for updates still existing in Mac when will be rectified for a professional company like Google

4:32 AM, September 14, 2014  
Blogger KiTA said...

Well, for a while there the "slow as mud when opening/closing windows and tabs" thing had vanished, but it's back. However it's not a hard freeze for a second or two anymore, just a bunch of very brief freezes over and over again.

Browsers aren't supposed to have a framerate. I hope this gets fixed soon.

9:59 AM, September 14, 2014  
Blogger Jasmine said...

There's an issue with Windows 8.1 touch screen computers that run Shockwave; it makes programs that use it incredibly tiny. Chrome was the only browser that was the exception to this until this update. I'm honestly wondering why this is, because I HAVE to use shockwave. For now, there's no way around it and now it's completely unusable on every browser.

I'll try downgrading versions, but unless this issue gets fixed, I basically can't upgrade Chrome ever again. Great.

4:07 PM, September 14, 2014  
Blogger Steve Dowe said...

Good tip from George Halkias. Thanks.

5:05 AM, September 15, 2014  
Blogger inkin dom said...

Hi , a short question:
why doesn't this version exist in http://src.chromium.org/svn/releases ?

4:52 AM, September 16, 2014  
Blogger geeta threem said...

thanks for this great post George Halkias.
If you want to make money in BEAR/BULL share market- join our team.
Visit : www.3mteam.in or call at 9301304732.
Email : enquiry@3mteam.in.

1:49 AM, September 17, 2014  
Blogger geeta threem said...

thanks for this great post George Halkias.
If you want to make money in BEAR/BULL share market- join our team.
Visit : www.3mteam.in or call at 9301304732.
Email : enquiry@3mteam.in.

1:49 AM, September 17, 2014  
Blogger Dave Raveling said...

So I was having issues with getting stuck in loops due to the "print preview" feature. Since this update I can't seem to recreate the issue. Was there by chance an update within Chrome to fix this issue?

8:50 AM, September 19, 2014  
Blogger Tom G said...

Updated last nite to 37.0.2062.120 m
and found every few minutes a new window spawns. Woke up this morning and had 23 chrome windows stacked up on my screen. WTF

3:54 AM, September 21, 2014  
Blogger Hideki Saito said...

On Linux (Linux 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux), this version (actually whole 37. x) is horrendously slow, especially for Omnibox, and other completion.

Looks like these are where it's choking...

Histogram: Omnibox.FocusToEditTime recorded 18 samples, average = 4142.1 (flags = 0x1)
Histogram: Omnibox.FocusToOpenTimeAnyPopupState recorded 17 samples, average = 14945.6 (flags = 0x1)

12:59 AM, September 22, 2014  
Blogger Diane said...

Version 37.0.2062.120 m stopped ability to copy and paste an image in Outlook email!! Terrible update

9:07 AM, September 22, 2014  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home