Thursday, February 2, 2012

Dev Channel Update

 The Dev channel has been updated to 18.0.1025.3 for Windows, Mac, Linux and Chrome Frame.  This build contains following stability and bug fixes:
  • Fixed URL handling of settings page. [Issue: 111900]
  • Fixed crash when unpacking extension. [Issue: 112301]
  • Fixed the case where the utility process crashes after all plugins have been loaded. [Issue: 111935]
Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels?  Find out how.  If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome

Labels:

12 Comments:

Blogger REO said...

Thanks again Google Dev Team! :)

7:02 PM, February 02, 2012  
Blogger Ashish Abraham said...

is that all with the settings page?

8:28 PM, February 02, 2012  
Blogger Przemys┼éaw Rumik said...

My problem (http://code.google.com/p/chromium/issues/detail?id=112444) still exists :-)
So problem with NTLM proxies.

2:52 AM, February 03, 2012  
Blogger I like 2 bee Anonymous said...

i used to be able to find this page
http://googlechromereleases.blogspot.com/

by hitting F1 and then it was close to left bottom but i dont see that anybody.

Please put it back there.

11:50 AM, February 03, 2012  
Blogger I like 2 bee Anonymous said...

When are we getting the master password for our saved passwords?

11:51 AM, February 03, 2012  
Blogger David Hergert said...

Also still having the crashing issue referenced in http://code.google.com/p/chromium/issues/detail?id=112444

Please provide instructions on how to actually get Chrome to startup and update itself.

12:20 PM, February 03, 2012  
Blogger Dogan said...

We can't use Chrome Web Store: http://code.google.com/p/chromium/issues/detail?id=106095

1:50 PM, February 03, 2012  
Blogger Cody said...

For those asking about the redesigned options page, see Issue 100885.

The "Uber Page" will include more chrome://x pages (ex: history) and will not be released in M18 Stable.

6:09 PM, February 03, 2012  
Blogger Marc said...

Is it just me or does each release seem to hog more memory and also manage memory worse?

I'm now using ~700mb just for the new tab screen. Memory doesn't seem to get released back to the OS efficiently when tabs are closed. If I open gmail, gdocs & 1 bank website, things slow to a crawl and sometimes doen't ever recover so I'm left with no choice but reboot.

Things have gotten so bad, that I think I may just head back to the beta release, something I haven't done since I received my Samsung Chromebook 2 days before they went on sale last year :(

1:40 PM, February 04, 2012  
Blogger Quill said...

@Marc
Fully agreed on the memory usage. Chrome team, what are you even doing? The browser was perfectly fine months ago, the only area where improvement is needed is the UI.

3:00 PM, February 04, 2012  
Blogger Seyss said...

the quality of these dev builds has drown recently

you keep introducing bugs and scaring us with shitty modifications like the options page

STOP WASTING TIME and implement missing MAJOR features already, like master password, ability to not collect history but keep cookies, and others.

look em up at http://www.google.mw/support/forum/p/Chrome/thread?tid=197b83f4f38c69cf&hl=en&fid=197b83f4f38c69cf000486e05ffe99a9&hltp=2

3:37 AM, February 06, 2012  
Blogger MakHooi said...

please fix this issue. (http://code.google.com/p/chromium/issues/detail?id=100021)
it has been there since chrome 15 beta until the latest chrome 19 canary.

12:39 AM, February 07, 2012  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home