Thursday, December 2, 2010

Stable, Beta Channel Updates

The Chrome team is happy to announce our latest Stable release, 8.0.552.215.  In addition to the over 800 bug fixes and stability improvements, Chrome 8 now contains a built in PDF viewer that is secured in Chrome’s sandbox.  As always, it also contains our latest security fixes, listed below.  This release will also be posted to the Beta Channel.

Security fixes and rewards:
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.
  • [17655] Low Possible pop-up blocker bypass. Credit to Google Chrome Security Team (SkyLined).
  • [55745] Medium Cross-origin video theft with canvas. Credit to Nirankush Panchbhai and Microsoft Vulnerability Research (MSVR).
  • [56237] Low Browser crash with HTML5 databases. Credit to Google Chrome Security Team (Inferno).
  • [58319] Low Prevent excessive file dialogs, possibly leading to browser crash. Credit to Cezary Tomczak (gosu.pl).
  • [$500] [59554] High Use after free in history handling. Credit to Stefan Troger.
  • [Linux / Mac] [59817] Medium Make sure the “dangerous file types” list is uptodate with the Windows platforms. Credit to Billy Rios of the Google Security Team.
  • [61701] Low Browser crash with HTTP proxy authentication. Credit to Mohammed Bouhlel.
  • [61653] Medium Out-of-bounds read regression in WebM video support. Credit to Google Chrome Security Team (Chris Evans), based on earlier testcases from Mozilla and Microsoft (MSVR).
  • [$1000] [62127] High Crash due to bad indexing with malformed video. Credit to miaubiz.
  • [62168] Medium Possible browser memory corruption via malicious privileged extension. Credit to kuzzcc.
  • [$1000] [62401] High Use after free with SVG animations. Credit to Sławomir Błażek.
  • [$500] [63051] Medium Use after free in mouse dragging event handling. Credit to kuzzcc.
  • [$1000] [63444] High Double free in XPath handling. Credit to Yang Dingning from NCNIPC, Graduate University of Chinese Academy of Sciences.
We would like to offer special thanks -- and a number of rewards -- to Aki Helin of OUSPG for his extensive help with the new PDF feature. We’d also like to extend thanks to Sergey Glazunov and Marc Schoenefeld for finding bugs during the development cycle such that they never reached a stable build.

Full details about the changes are available in the SVN revision log. If you find new issues, please let us know by filing a bug. Want to change to another Chrome release channel? Find out how.

Jason Kersey
Google Chrome

54 comments:

Cougar Abogado said...

Any web store hints (besides Chrome 8 being the first version capable of using the web store)?

Anon said...

I noticed the unicode support is slightly better, however, I still get empty boxes when viewing certain unicode characters.

Amit said...

Q: How is this versions' PDF reader different from the one that was included in Chrome 7?

iulian said...

URGENT. In my computer , the chrome is not working at all, i can,t open a single page with it. this happen after it upgrated to chrome 6.
hope you will resolve this,

g33k said...

Omg, this 8 version is 2-3x faster than previous version - good job developers.

Administrator said...

I liked last version's PDF viewer. better. If the background wasn't that grey more like a black or dark grey.

Groupa said...

how do I save the PDF document?

Vineet said...

The font on this one post looks terrible on my mac (in Chrome). The rest of the blog looks fine. Looks like HTML pasted in from somewhere (lots of Apple-style-span and explicit style attributes setting Helvetica Neue).

andrewhime said...

When can we expect a 64-bit version of Chrome for Windows?

qwe123123 said...

Agree with Amit that the pdf viewer was around in the previous stable as well. So to say it is new is a mis-statement.

Agree with Administrator that the darker background was more friendly.

qwe123123 said...

Must add that the difference is that the ver 8 pdf viewer is sandboxed. The ver 7 one wasn't.

Marcelo said...

===========BUG===========

I already said 100 times here. There is a bug that you don't repair: I have 400 bookmarks, and when I click in a letter (g, for exemple), in bookmarks folder (in bookmarks bar) Chrome doesn't show me my bookmarks that begin with letter g.

This is the cause I prefer Firefox...

It´s a pity, cause I said it 100 times HERE!

I am tired to say that!

Chris said...

@qwe123123: the PDF plug-in has always been sandboxed. What is new in version 8 is that it is _enabled by default_. It's also faster and has a few new features.

@Marcelo: this is not the correct place to tire yourself out reporting bugs! Please use the Chromium bug tracker.

Cougar Abogado said...

@Marcelo. Here's a link to an entry form for the bug list Chris's talking about: http://code.google.com/p/chromium/issues/entry.

For a general overview of issues (if you want to get a general idea of how people file bugs, etc.), go here: http://code.google.com/p/chromium/issues/list

Hope this helps.

qwe123123 said...

Chris, to sandbox plug-ins we had to use --safe-plugins.

If you're 100% sure that the pdf viewer was sandboxed from day 1, I won't argue.

Even Flash is in the process of being sandboxed, IMO.

Incidentally, the pdf viewer made it's first appearance in the stable of version 6. See this for example: http://www.google.com/support/forum/p/Chrome/thread?tid=3413d3e34dda5cf2&hl=en

To my mind, there's some inadvertent misreporting about when exactly the Chrome PDF Viewer made its debut in Chrome stable.

Coming back to the present, I briefly looked at the PDF viewer and haven't found any new features. I'll look more carefully!

Of course, if you'll be kind enough to list them (without asking me to go through the changelog ;)), I'd be most grateful.

Ilia said...
This comment has been removed by the author.
qwe123123 said...

There's no link to the SVN revision log!

qwe123123 said...

Sorry, I found the SVN rev. log.

Amit, one difference between the old and new PDF viewer is that we can copy more text than was previously possible.

GroupA, if you right-click on the page displaying the pdf, you'll get "save as"

JadeDragon said...

Man Chrome is just so much faster than IE on my older laptop. Keep up the good work everyone on the Chrome team.

qwe123123 said...

I should not have questioned Google's security expert when he said that the PDF viewer was sandboxed from day 1:
http://blog.chromium.org/2010/06/improving-plug-in-security.html

ritesh said...

thanks for a good information crome is best faster browser.

http://vritesh.com

Yuk Fai said...

I found some PDFs cannot be saved while some can.

http://code.google.com/p/chromium/issues/detail?id=65305

manny said...

this is great progress with the pdf reader.

What chrome needs now is an ODF reader. Maybe even provide a link to modify it with gdocs.

I assume these functionalities will be also land in chromeOS

Pixel Buffer said...

Is there still no embedded pdf viewer in Chromium for Linux? I just installed 5.0.552.215 and when I click on a pdf link it just downloads the file. Then when I click on the filename in the download bar, it launches Firefox, which in turn starts acrobat reader. Is there any way around this?

MatejB said...

Cool PDF viewer. But spell checker is still not working good. I have to click on every single word in text box area when I switch language (to underline spell mistakes).

Nick said...

Have tried previous versions of Chrome on my Vista SP2 64Bit machine and I am unable to close it using the top right X ? A major bug or just happens to me ? On my XP SP3 machine, works great.

gonder said...

I updated Chrome to 8.0.552.215 last stable release. But it doens't open any pages. Only shows blank page. When i type something in address bar it shows suggestions but can't open. I uninstalled and reinstalled, deleted data folder but it didn't work.
OS: Windows 7, Firewall: Online Armor (Not blocking Chrome)
Update:
I added --no-sandbox flag and now it works. But it says "You are using an unsupported command-line flag: --no-sandbox. Stability and security will suffer." Is it safe to use Chrome like that?

Victor said...

While this is a big improvement over Chrome 7.x, 8 still fails on some important points:

1) Some pages either don't load at all or load with missing images -- including ironically this blog. This seems to be exacerbated when you open multiple pages in tabs on startup, i.e. 11 tabs +. This happens even on well known sites such as nytimes.com!!!!

2) Flash doesn't work everywhere.

True Chrome 8 is fast -- but only if the page loads. Therefore should we count reload times as part of the page loading times????

gonder said...

Chrome 8.0.552.215 stable final release only works with "--no-sandbox" flag And it says "You are using an unsupported command-line flag: --no-sandbox. Stability and security will suffer." Why? Please help!!!!!!!!!!!

Marc said...

FINALLY!

The ever-present problem of chrome freezing up when accessing gmail.com (http://www.google.com/support/forum/p/Chrome/thread?tid=636c157ca0cd4261) has been fixed.

Thanks so much, guys.

Sir said...

This is the worst I've seen from Google Chrome by far. Very, very unstable and slow. No plug-ins work, nor do images load. All websites are broken and do not display correctly.

Sarcastically, the best of all, I cannot revert to my previous version. Google Chrome 9 is coming out soon and you aren't even close to finishing Chrome 8. Google, you're sounding more and more like Microsoft.

NOTE:

-This is for Google Chrome 8.0.552.215 for Windows Vista 64-bit.

-8.0.552.215 for Mac OS X 10.6.5 64-bit is working as it should.

I do understand this is BETA.

Terry said...

The update blog has specifics about the security fixes, but is there a way to see what's new in terms of 'featurs' for users?

Seán O'Neill said...

Amazing work, truly impressive.

mathetos said...

I tried to save a PDF from within the browser with right click, save as... and it corrupted the file somehow. Was able to download the same exact file in IE no problem. I also think there are many tools within Adobe Reader that need to be available somehow when viewing PDFs online within the browser. Perhaps expand the right click menu, or the zoom menu that appears on the bottom right (which is awesome, but limited).

Marco said...

there is a bug with google maps: if i use scroll to zoom in/out, after it i can't move map holding left button of mouse.

enoperiplos said...

@Nick Same here, Vista SP2 32bits.

Atique said...

I am running Windows 7. This stable release won't install. It says Side by Side configuration is incorrect!

Should it happen with a stable release?

Previous stable releases are okay. But this version is giving me headache. I cannot get to install it.

Hoping to find a solution..

nathan said...

@Pixel Buffer: The PDF viewer is in Google Chrome only, not Chromium. It works on Linux if you have Google Chrome, but not with Chromium.

ryan said...

hi -- is there a way I can revert back to the previous release?

I was doing some development which integrates with Chrome, and it has suddenly broken, and I think I have narrowed it down to being introduced by the update. I would like to revert just to confirm that this is where the error was introduced -- then I can try to fix it.

Cheers.

Smuggy said...

it still says that there is anew version of Chrome when you check for updates (then gives you an error) - Update Server Not Available error: 12


I'm already on the latest stable 8.0.552.215

Mac OS X Snow Leopard 10.6.5

Parimal said...

On auto update of Chrome to 8.0.552.215 on Mac OS X 10.5.8, i am getting a bus error (chrome is crashing) when trying to pack my chrome extension from command line.

Crash reporter is pointing at
Thread 1 Crashed:
0 com.google.Chrome.framework 0x03912607 ChromeMain + 8531063
1 libSystem.B.dylib 0x9703d155 _pthread_start + 321
2 libSystem.B.dylib 0x9703d012 thread_start + 34

My build process is completely screwed. I am using this command from terminal:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --pack-extension=$PWD/osx/cloudmagicplugin@webyog -pack-extension-key=$PWD/cloudmagicplugin@webyog.pem

Please tell me if anything is changed here?

TIA
Parimal Das

Edward said...

Just tried IE9 beta. Sticking with Chrome.

nonsense streamer said...

the new pdf viewer seems elegant and loads faster, however now I can't define the background color!

I like reading black on grey, I should have the option to choose the background color.

gayuh said...

thanks for sharing, please visit me back

Fabio_Rulez said...

@Victor: try eliminate DNS prefetching on the under the wood section of options (uncheck it). this may fix your issue.

dteare said...

@Parimal: I am having the exact same issue. The new Chrome crashes every time when building extensions from the command line.

Please confirm you're having the same problem to "vote up" this issue:

http://code.google.com/p/chromium/issues/detail?id=65645

Anthony said...

Is there some way to get around the new in-browser pdf reader (which looks, feels, and acts like a crippled version of Adobe) and open pdf files in a separate Adobe window as I used to do?

Alex said...

No chance to view PDF files arriving from the Adobe Livecycle (i.e., forms)? What a shame... Chrome is such a cool browser otherwise!

Vamsi said...

I keep getting a lot of "Aw..Snap" errors after this update!

What's happening!?

Scott Supak said...

This version, 8.0.552.215, is now wreaking havoc with my right aligned tables. It's not allowing anything to the left of the table that's aligned right. So, now text wrapping left around a table that is floating right.

I know I'm using old HTML and not enough CSS, but I have a lot of sites that do this old style and I'm screwed if tables can't float now.

Please someone tell me this is a bug that will get fixed!

Fabio_Rulez said...

@Anthony: type about:plugins in the omnibox, disable PDF chrome viewer and enable adobe ones

Atique said...

> I am running Windows 7. This stable release won't install. It says Side by Side configuration is incorrect!

Redownloaded the file. It's okay now. Thanks a lot.

ianp said...

Crash occurs when "clear all browsing data" via History -> Edit Items -> Clear all browsing data on Google Chrome v8.0.552.215 Stable

more info here: http://code.google.com/p/chromium/issues/detail?id=66658

Roedy said...

It would be nice if you posted the versions of the current downloads at
http://www.google.com/chrome