Chrome 13 Is Officially Out ! Adds Instant Pages and print preview

[Jack]

The Google Chrome team is pleased to announce the arrival of Chrome 13.0.782.107 to the Stable Channel for Windows, Mac, Linux, and Chrome Frame. Spanning 5200+ revisions, Chrome 13 contains some exciting new features like Instant Pages prerendering technology. To find out about other new features, check out the Official Chrome Blog.

Security fixes and rewards: - link

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.

[75821] Medium CVE-2011-2358: Always confirm an extension install via a browser dialog. Credit to Sergey Glazunov.
[$1000 each] [78841] High CVE-2011-2359: Stale pointer due to bad line box tracking in rendering. Credit to miaubiz and Martin Barbella.
[79266] Low CVE-2011-2360: Potential bypass of dangerous file prompt. Credit to kuzzcc.
[79426] Low CVE-2011-2361: Improve designation of strings in the basic auth dialog. Credit to kuzzcc.
[Linux only] [81307] Medium CVE-2011-2782: File permissions error with drag and drop. Credit to Evan Martin of the Chromium development community.
[83273] Medium CVE-2011-2783: Always confirm a developer mode NPAPI extension install via a browser dialog. Credit to Sergey Glazunov.
[83841] Low CVE-2011-2784: Local file path disclosure via GL program log. Credit to kuzzcc.
[84402] Low CVE-2011-2785: Sanitize the homepage URL in extensions. Credit to kuzzcc.
[84600] Low CVE-2011-2786: Make sure the speech input bubble is always on-screen. Credit to Olli Pettay of Mozilla.
[84805] Medium CVE-2011-2787: Browser crash due to GPU lock re-entrancy issue. Credit to kuzzcc.
[85559] Low CVE-2011-2788: Buffer overflow in inspector serialization. Credit to Mikołaj Małecki.
[$500 each] [85808] Medium CVE-2011-2789: Use after free in Pepper plug-in instantiation. Credit to Mario Gomes and kuzzcc.
[$1000] [86502] High CVE-2011-2790: Use-after-free with floating styles. Credit to miaubiz.
[$1000] [86900] High CVE-2011-2791: Out-of-bounds write in ICU. Credit to Yang Dingning from NCNIPC, Graduate University of Chinese Academy of Sciences.
[$1000] [87148] High CVE-2011-2792: Use-after-free with float removal. Credit to miaubiz.
[$1000] [87227] High CVE-2011-2793: Use-after-free in media selectors. Credit to miaubiz.
[$500] [87298] Medium CVE-2011-2794: Out-of-bounds read in text iteration. Credit to miaubiz.
[$500] [87339] Medium CVE-2011-2795: Cross-frame function leak. Credit to Shih Wei-Long.
[87548] High CVE-2011-2796: Use-after-free in Skia. Credit to Google Chrome Security Team (Inferno) and Kostya Serebryany of the Chromium development community.
[$1000] [87729] High CVE-2011-2797: Use-after-free in resource caching. Credit to miaubiz.
[87815] Low CVE-2011-2798: Prevent a couple of internal schemes from being web accessible. Credit to sirdarckcat of the Google Security Team.
[$1000] [87925] High CVE-2011-2799: Use-after-free in HTML range handling. Credit to miaubiz.
[$500] [88337] Medium CVE-2011-2800: Leak of client-side redirect target. Credit to Juho Nurminen.
[$1000] [88591] High CVE-2011-2802: v8 crash with const lookups. Credit to Christian Holler.
[88827] Medium CVE-2011-2803: Out-of-bounds read in Skia paths. Credit to Google Chrome Security Team (Inferno).
[$1000] [88846] High CVE-2011-2801: Use-after-free in frame loader. Credit to miaubiz.
[$1000] [88889] High CVE-2011-2818: Use-after-free in display box rendering. Credit to Martin Barbella.
[$500] [89142] High CVE-2011-2804: PDF crash with nested functions. Credit to Aki Helin of OUSPG.
[$1500] [89520] High CVE-2011-2805: Cross-origin script injection. Credit to Sergey Glazunov.
[$1500] [90222] High CVE-2011-2819: Cross-origin violation in base URI handling. Credit to Sergey Glazunov.

In addition, we would like to thank David Levin, Kostya Serebryany, John Abd-El-Malek and Darin Fisher of the Chromium development community, “daduck10” and Collin Payne for working with us in the development cycle and preventing bugs from ever reaching the stable channel. Various rewards were issued.

Thanks again to all the security researchers we work with. There are $17,000 of rewards in this patch, which is possibly the best haul yet.

New added features :

Instant Pages is on by default in the latest stable version of Chrome. This means that sometimes when you click a Google search result in Chrome, the page will appear to load much faster than before. How much faster? In the video below, you can see a side by side comparison of Chrome with and without Instant Pages enabled.



Print preview is available for Windows and Linux users in the latest stable version of Chrome.
Many people have been asking for print preview in Chrome for a long time, and Google wanted to do it right, using their fast built-in PDF viewer and an easy “print to PDF” option.

 

[Hungry Man]

Not what I'd call an exciting version. Though it would have been nice if they'd brought up the security benefits of Chrome 13's new certificate validation techniques.

 

[illumination]

I am test driving this right now

 

[Dejan]

I'm going to try this out and see if pages load better and faster.

Edit: First impressions are good, pages seem to load significantly faster than before. I'll use it some more to see if I get any of the past issues (where pages don't load correctly or take too long to load).
Edit 2: LastPass and WOT aren't working on this version, probably because they weren't updated yet. I'll wait some more if I decide to use Chrome more often.

 

[Ink]

LastPass and WOT are working, version 13.0.782.107.

This version also has the hidden toolbar.

Compact Navigation
Adds a "Hide the toolbar" entry to the tab strip's context menu. Use this to toggle between always displaying the toolbar (default) and only opening it as a drop-down box, as needed.

I'm not a fan of the Instant Pages.

 

[win7holic]

i never use chrome again. since 2,5 years ago.
but, i want use it again.
i don't like with lot processes by chrome (can until 7 or more)

 

[Ink]

i don't like with lot processes by chrome (can until 7 or more)

Multiple process web browser are becoming a norm. Nothing you should be worrying about.

 

[jamescv7]

Yes but yet useful thing why Chrome have numerous processes.

From this post by Jack the explanation was clear.

 

[win7holic]

i don't like with lot processes by chrome (can until 7 or more)

Multiple process web browser are becoming a norm. Nothing you should be worrying about.

yeah i know it. but, such as firefox? firefox use 1 processes ,even open lot tabs
i open firefox with 4 tabs just use 222MB now (1 processes).

 

[Ink]

With so many potential points of failure, it’s up to the browser makers to ensure that everything runs smoothly and securely. One way of doing this is by splitting the browser process into several components and isolating them from each other. This ensures that if one of them fails, it doesn’t bring down the entire browser. For example, if a site has buggy or malicious code, it may crash a tab, but it won’t affect the others or the browser as a whole.

Multi-Processes in Browsers: Chrome, Internet Explorer, Firefox and WebKit

Running multiple processes is handy too, say if, I want to terminate an extension. I launch the task manager in Chrome and terminate that process. (ie. I don't always need WOT or AdBlock Plus running, but I don't want to permanently disable it either).

 

[jamescv7]

Its a myth that a browser is good with only one process unlike the another browser with numerous process.

 

[win7holic]

ok storm, will give it try out later
use chrome again.

 

[Hungry Man]

Multi-Processes is the best thing ever =p

Also, Firefox uses two. Though it may as well only use one in terms of security.

 

[jamescv7]

The one processes was plugin-container.exe which was connected when watching videos.

Processes must be same like the Chrome or IE, same processes name and can be equalized the usage from that process.

 

[win7holic]

Multi-Processes is the best thing ever =p

Also, Firefox uses two. Though it may as well only use one in terms of security.

firefox.exe and plugin-container.exe
plugin container use 17MB of ram.

 

[Jack]

Edit 2: LastPass and WOT aren't working on this version, probably because they weren't updated yet. I'll wait some more if I decide to use Chrome more often.

I have Google 13 on my system .. and all the add-ons work perfectly....
[attachment=704]
You can try a uninstall/re-install for the add-ons to fix the problem.If the problem persists just uninstall/re-install Chrome.
I for one love the Instant loading feature.....I;ve also enable in about:flags - Preload Instant Search (Preload the default search engine for Instant.)
Overall I feel like Chrome it's the fastest browser out there.

 

[Hungry Man]

In terms of rendering and javascript Chrome 13 and Firefox 8 Nightly are apparently very close.

The fact is that Chrome still pulls ahead because of its prerendering features. Preloading webpages as you type them (prerender from omnibox is in 14) and preloading instant results/ search engines puts it ahead.

Plus the fact that Chrome has consistently managed to pull ahead of other browsers, though not quite as much lately. When it first came out it was insane how different the speed was. Now other browsers have caught on and have started to compete thankfully.

 

[Ink]

Has anyone else found the predictive URL to be slower?

---

I also noticed they added a FPS column to the Chrome 'Task Manager'.

[attachment=712]

 

[Hungry Man]

Yup. FPS for the GPU accelerated tabs. It's nice because you get to see which tabs are accelerated.

I haven't noticed predictive URL's being slower but I would not be surprised considering that it's only just made it to stable.