Monday, January 31, 2011

Dev Channel Update


The Chrome Dev channel has been updated to 10.0.648.11 for all platforms.  This build contains stability fixes and refinements to the new settings pages. Update: This release will reset any flags you had set. You can set them again in about:flags. Full details about the Chrome 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

Labels:

26 Comments:

Blogger jzero15 said...

All my flags seem to have been reset and have to re-enable them again.

8:11 PM, January 31, 2011  
Blogger REO said...

So far, so good.

Thanks Google Dev Team.

Win Vista/32 bit

8:13 PM, January 31, 2011  
Blogger chjj said...

Video playback still seems to break a page entirely for me. Interactive content doesn't hover or focus properly.

8:16 PM, January 31, 2011  
Blogger Pratik Thakkar said...

All my flags have been reset with this update.

9:35 PM, January 31, 2011  
Blogger Adam W. said...

Nice "close" option in Tab Overview! Even more useful and elegant.

11:00 PM, January 31, 2011  
Blogger D.K. said...

I get immediate crash after update on a Mac Pro running 10.6.6. Here's a stack trace excerpt:

Thread 0 Crashed: CrBrowserMain Dispatch queue: com.apple.main-thread
0 com.google.Chrome.framework 0x0053d8c9 ChromeMain + 5460793
1 com.google.Chrome.framework 0x00541377 ChromeMain + 5475815
2 com.google.Chrome.framework 0x005356dd ChromeMain + 5427533
3 com.google.Chrome.framework 0x00512033 ChromeMain + 5282467
4 com.google.Chrome.framework 0x01199ddb ChromeMain + 18421835
5 com.google.Chrome.framework 0x009081cc ChromeMain + 9436220
6 com.google.Chrome.framework 0x0090837e ChromeMain + 9436654
7 com.google.Chrome.framework 0x00908fbb ChromeMain + 9439787
8 com.google.Chrome.framework 0x008e0694 ChromeMain + 9273604
9 com.apple.CoreFoundation 0x93a004cb __CFRunLoopDoSources0 + 1563
10 com.apple.CoreFoundation 0x939fdf8f __CFRunLoopRun + 1071
11 com.apple.CoreFoundation 0x939fd464 CFRunLoopRunSpecific + 452
12 com.apple.CoreFoundation 0x939fd291 CFRunLoopRunInMode + 97
13 com.apple.HIToolbox 0x98da1004 RunCurrentEventLoopInMode + 392
14 com.apple.HIToolbox 0x98da0dbb ReceiveNextEventCommon + 354
15 com.apple.HIToolbox 0x98da0c40 BlockUntilNextEventMatchingListInMode + 81
16 com.apple.AppKit 0x968ad78d _DPSNextEvent + 847
17 com.apple.AppKit 0x968acfce -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
18 com.apple.AppKit 0x9686f247 -[NSApplication run] + 821
19 com.google.Chrome.framework 0x008e0415 ChromeMain + 9272965
20 com.google.Chrome.framework 0x008df8ca ChromeMain + 9270074
21 com.google.Chrome.framework 0x00908e64 ChromeMain + 9439444
22 com.google.Chrome.framework 0x001be532 ChromeMain + 1793954
23 com.google.Chrome.framework 0x000092af ChromeMain + 3359
24 com.google.Chrome 0x00001f58 0x1000 + 3928
25 com.google.Chrome 0x00001f16 0x1000 + 3862

---

Clearing the Library/../Chrome/* helps, re-enabling Sync results in a crash.

---

11:16 PM, January 31, 2011  
Blogger Mesca Vlad said...

my chrome sey:a comand line unsuported: --enable-nacl. Stability & security ... I don't use a comand like this.

12:25 AM, February 01, 2011  
Blogger ChRiStOpHe said...

I've also the crash at startup under OSX 10.6.6

Process: Google Chrome [3363]
Path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier: com.google.Chrome
Version: 10.0.648.11 (648.11)
Code Type: X86 (Native)
Parent Process: launchd [117]

Date/Time: 2011-02-01 09:29:38.471 +0100
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6

Interval Since Last Report: 206 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 1 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 74A5B3E1-38E2-4B7B-BF5F-F3603FB650C7

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

12:31 AM, February 01, 2011  
Blogger Desparanso said...

Seems you've removed "Click to play" on plugin options - I used this function regular. Please bring it back.

12:42 AM, February 01, 2011  
Blogger Rohit said...

This version of chrome is also crashing for me at startup under Mac OS X 10.6

2:20 AM, February 01, 2011  
Blogger Hugo Arag´┐Żo Correia said...

On OsX 10.6.6 no crash, but flags reseted.

4:31 AM, February 01, 2011  
Blogger Maik Kulbe said...

Lol seems like the stability fixes are crashing my chrome-.- When I try to start chrome it instantly freezes( under Ubuntu Lucid)

5:01 AM, February 01, 2011  
Blogger Chris said...

@desparanso the feature is still there, the flags were reset, go to the about:flags page and re-enable click to play

7:41 AM, February 01, 2011  
Blogger Andrea said...

PLUGIN ADOBE SCHOCKWAVE PLAYER (LATEST VERSION (11.5.9.615)CRASH!
WHY DON'T YOU FIX THIS PROBLEM?
:-(((

9:40 AM, February 01, 2011  
Anonymous Anonymous said...

- Flags are reset upon update on Windows and Linux.

- Enabling Native Client in about:flags produces a Error message upon start of the Browser ("You are using an unsupported command-line flag: --enable-nacl. Stability and security will suffer.") on Windows and Linux.

Way to go, Google ...

11:25 AM, February 01, 2011  
Blogger Sagi Koren said...

Still having trouble syncing the account.
Asking for old Passphrase and non of the passwords I remember work.

11:29 AM, February 01, 2011  
Blogger sabih said...

You are using an unsupported command-line flag: --enable-nacl. Stability and security will suffer

11:42 AM, February 01, 2011  
Blogger Rick said...

Disabling 'Native Client' resolves the unsupported command line message.

11:55 AM, February 01, 2011  
Blogger molumen said...

Lots of crashes on pages with Flash, also lots of crashes on www.wordsquared.com.
And tons of random crashes all around.. Previous dev release was surprisingly a lot more stable.

12:44 PM, February 01, 2011  
Blogger molumen said...

Dunno if anyone noticed, but the "learn more" link on the crash page doesn't work :)

12:56 PM, February 01, 2011  
Blogger Jason Kersey said...

Please be sure to submit crashes when they occur. If you have a crash ID, I can also check that. Especially interested in the crash on start for Mac that people have mentioned.

1:58 PM, February 01, 2011  
Blogger Sebastian said...

Crashes on start *every* time; Mac OS X 10.6.6. Here's the full error: http://pastie.org/1520034

4:18 PM, February 01, 2011  
Anonymous Anonymous said...

A lot of crashes with Farmville in Facebook (when I close the request gift window)

5:08 PM, February 01, 2011  
Blogger 8ball said...

@alehox,
it's not a bug, it's a feature so you would quit, grow up and get a life.

9:07 PM, February 02, 2011  
Blogger Destroyzer said...

orkut don't load in this build, only in private window.

7:56 AM, February 03, 2011  
Blogger Kristopher Perovic said...

Found this forum by means of Googling.

I'm running Chrome OS version 0.10.155.4-11.02.01 on my Cr-48 and I, in an effort to experiment, enabled everything under chrome://flags. Now no websites will load once I log in as a registered user or a guest -- my settings won't load, nothing will load except a blank page and a message across a yellow bar that reads, "You are using an unsupported command-line flag: --enable-nacl. Stability and security will suffer."

Can anyone help me get my brand new Cr-48 back to normal?

Please email me at kperovic@gmail.com

6:22 PM, February 09, 2011  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home