Thursday, April 5, 2012

Stable and Beta Channel Updates


The Chrome Stable and Beta channels have been updated to 18.0.1025.151 on Windows, Mac, Linux and Chrome Frame.  This release fixes issues including:
  • black screen on Hybrid Graphics system with GPU accelerated compositing enabled (Issue: 117371)
  • CSS not applied to <content> element (Issue: 114667)
  • Regression rendering a div with background gradient and borders (Issue: 113726)
  • Canvas 2D line drawing bug with GPU acceleration (Issue: 121285)
  • Multiple crashes (Issues: 72235116825 and 92998)
  • Pop-up dialog is at wrong position (Issue: 116045)
  • HTML Canvas patterns are broken if you change the transformation matrix (Issue: 112165)
  • SSL interstitial error "proceed anyway" / "back to safety" buttons don't work (Issue: 119252)
Known Issues:
  • HTML5 audio doesn't work on some Mac computers (Issue: 109441)
Security fixes and rewards:

A new version of Flash Player is included. More details are available in an addendum to this Flash Player advisory.

Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

  • [$500] [106577] Medium CVE-2011-3066: Out-of-bounds read in Skia clipping. Credit to miaubiz.
  • [117583] Medium CVE-2011-3067: Cross-origin iframe replacement. Credit to Sergey Glazunov.
  • [$1000] [117698] High CVE-2011-3068: Use-after-free in run-in handling. Credit to miaubiz.
  • [$1000] [117728] High CVE-2011-3069: Use-after-free in line box handling. Credit to miaubiz.
  • [118185] High CVE-2011-3070: Use-after-free in v8 bindings. Credit to Google Chrome Security Team (SkyLined).
  • [118273] High CVE-2011-3071: Use-after-free in HTMLMediaElement. Credit to pa_kt, reporting through HP TippingPoint ZDI (ZDI-CAN-1528).
  • [118467] Low CVE-2011-3072: Cross-origin violation parenting pop-up window. Credit to Sergey Glazunov.
  • [$1000] [118593] High CVE-2011-3073: Use-after-free in SVG resource handling. Credit to Arthur Gerkis.
  • [$500] [119281] Medium CVE-2011-3074: Use-after-free in media handling. Credit to Sławomir Błażek.
  • [$1000] [119525] High CVE-2011-3075: Use-after-free applying style command. Credit to miaubiz.
  • [$1000] [120037] High CVE-2011-3076: Use-after-free in focus handling. Credit to miaubiz.
  • [120189] Medium CVE-2011-3077: Read-after-free in script bindings. Credit to Google Chrome Security Team (Inferno).

Many of these bugs were detected using AddressSanitizer.



More detailed updates are available on the Chrome Blog.  Full details about what changes are in this release are available in the SVN revision log.  Interested in hopping on the stable channel?  Find out how.  If you find a new issue, please let us know by filing a bug.

Karen Grunberg
Google Chrome

17 comments:

Mainman678 said...

WOW new stable update already. So far no crashes. I will update it any.

Ka'Dield said...
This comment has been removed by the author.
Migman said...

Both versions hang at Google+ and VK.com. =(

Louis said...

Hello,

both problems with "GPU Composting..." enabled still remain unfixed.A nice cap of the now legendary fraking blue bar (See my post about the previous build for the first problem):

http://tinypic.com/r/qohlw4/5

Obtained by simply pressing F11 repeatedly.
What a PITA,Ms Grunberg,because the rest works flawlessly.

PS:
chrome://gpu/
Log Messages
• [4860:4388:1122017296:ERROR:gpu_info_collector_win.cc(68)] : CoCreateInstance() failed
• [4860:4388:1122017296:INFO:gpu_child_thread.cc(110)] : gpu_info_collector::CollectGraphicsInfo complete. success = 1
• [4860:4388:1122017500:ERROR:gl_surface.cc(87)] : NOT IMPLEMENTED
• [4860:4388:1122027703:ERROR:gl_surface.cc(87)] : NOT IMPLEMENTED
• [4860:4388:1123009843:ERROR:gl_surface.cc(87)] : NOT IMPLEMENTED
• [4860:4388:1123240359:ERROR:gl_surface.cc(87)] : NOT IMPLEMENTED
• [4860:4388:1123292093:ERROR:gl_surface.cc(87)] : NOT IMPLEMENTED
• [4464:5676:1123310406:ERROR:gpu_info_collector_win.cc(68)] : CoCreateInstance() failed
• [4464:5676:1123310406:INFO:gpu_child_thread.cc(110)] : gpu_info_collector::CollectGraphicsInfo complete. success = 1
• [4860:4388:1123339343:ERROR:gl_surface.cc(87)] : NOT IMPLEMENTED

Bob said...

Chrome (18.0.1025.151) just started crashing with this new version immediately on startup. I'm running Mac OS X 10.7.2 (11C74) on a Macbook Pro 3.06 GHz Intel Core2Duo. I found a very old Chrome (v4) that runs fine. Please back off this "stable" release.

Thanks.
LABobby@gmail.com


Here's stack info:
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000005038aabf

VM Regions Near 0x5038aabf:
mapped file 0000000004fe1000-000000000543a000 [ 4452K] r--/r-x SM=PRV /Applications/Google Chrome.app/Contents/Versions/18.0.1025.151/Google Chrome Framework.framework/Resources/resources.pak
-->
MALLOC_TINY 0000000069600000-0000000069700000 [ 1024K] rw-/rwx SM=COW

Application Specific Information:
objc[4981]: garbage collection is OFF

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 com.google.Chrome.framework 0x00308980 ChromeMain + 2363648
1 com.google.Chrome.framework 0x00308fc1 ChromeMain + 2365249
2 com.google.Chrome.framework 0x004c564b ChromeMain + 4185547
3 com.google.Chrome.framework 0x004d7e41 ChromeMain + 4261313
4 com.google.Chrome.framework 0x004d7644 ChromeMain + 4259268
5 com.google.Chrome.framework 0x004d6cc8 ChromeMain + 4256840
6 com.google.Chrome.framework 0x004d69dc ChromeMain + 4256092
7 com.google.Chrome.framework 0x004d62e8 ChromeMain + 4254312
8 com.google.Chrome.framework 0x0023d6e2 ChromeMain + 1531490
9 com.google.Chrome.framework 0x0023d263 ChromeMain + 1530339
10 com.google.Chrome.framework 0x01fa56f0 ChromeMain + 32366192
11 com.google.Chrome.framework 0x01fa4ecf ChromeMain + 32364111
12 com.google.Chrome.framework 0x0089ad8d ChromeMain + 8205581
13 com.google.Chrome.framework 0x000c78a9 ChromeMain + 41
14 com.google.Chrome 0x000c0f58 main + 24
15 com.google.Chrome 0x000c0f16 0xc0000 + 3862


Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x038cb158 ebx: 0xc00be138 ecx: 0x000fc080 edx: 0x0006f4c0
edi: 0x5038aabb esi: 0x038c8760 ebp: 0xc00be178 esp: 0xc00be120
ss: 0x00000023 efl: 0x00010206 eip: 0x00308980 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x5038aabf
Logical CPU: 0

Rafael said...

In either check I discovered the flaw that is causing freezes on the pages while I'm rolling them down or up. I think it's the flash player that is making Google Chrome freezing can fix this please? This has happened since the first released version 17 version 16 in Google Chrome behaved perfectly. You can not use Google Chrome with so many failures and crashes.

Bob said...

I could never get Chrome 18.0.1025.151 to work (reinstalling multiple times, cleaning things out, etc.).

However, I moved to the latest dev release (Version 19.0.1084.9 dev) which is working fine.

I know this wasn't the intent, but a "stable" release should never be so bad that it's entirely broken on standard hardware.

Thanks to whoever fixed the problem in the later dev release!

Thanks,
Bob

Casey said...

There seems to be some serious bugs in the "stable" version of Chrome 18. I'm currently developing a web app that has been working flawlessly in 17 and now crashes frequently. I've read reports online of Facebook, Rdio and even Google+ having the same problems. Are you guys aware and/or looking into this? It's a huge deal for us, we were going to launch a public beta next week and we're requiring Chrome Frame for IE which I assume has the same issue. Ugh.

ADRENALINE said...

-Canvas 2D line drawing bug with GPU acceleration (Issue: 121285)

yeeeee... now webgl is working again (for me)...

Tanmoy said...

chrome 18 sync ask many time for password after successful sync

Masloozinit76 said...

This update is horrible! Facebook bgean crashing every few minutes almost immediately and is still doing it. Now it is more than facebook (and that was no games running, just trying to update status it would crash). Now any webpages that are open will crash! I wish I could revert back to an older, working version!

allbangladeshinewspaper said...

Get excursive WordPress themes full free premium themes in this site.
This is a nice web site. Good fresh interface and nice informative articles. I will be coming back soon, thanks for the great article.
Skin Cancer
dse
free wordpress themes

internetbusiness said...

extension won't work, how do i get back to previous version, please help me, in urgent.

msi2 said...

if anyone want to get older version, you need to go to filehippo or oldapps.

Vitus Capital said...
This comment has been removed by the author.
Vitus Capital said...

According to Task Manager this version (with new flash) gets flash using up to 100% on one cpu fairly easily. Sometimes I can get it down to 15+/-% by randomly closing tabs.

For now, back to FF. (yuk)

Thanks

MBA 4,2 - Lion

Sacriven said...

My GC are error right now. When I start it, the tab doesn't work and always showing "Terminate the tab". Sometimes the 0xc0000005 error appears. What should I do?