Tuesday, November 6, 2012

Dev Channel Update

The Dev channel has been updated to 24.0.1312.5  for Windows, Mac, Linux, and Chrome Frame.  This build contains following updates:


  • Fixed BrowserFrameWin artifact on opaque to glass frame changes. (Issue: 156982)
  • Fixed a crash that could occur if the user closed a tab with an uncommitted search navigation. (Issue: 158201)
  • Fixed focus issue which does not change from Omnibox to Find in Page on mouseclick. (Issue: 158562)
  • Flash Mac: Fixed escape to exit fullscreen. (Issue: 155492)
  • Fixed crash when installing an extension and the browser window goes away. (Issue: 134194)
  • Ensure sidebar links are re-enabled when a confirmation dialog is closed. (Issue: 158912)
  • Fixed old Chrome version cleanup. (Issue: 75951)
  • Fixed memory leak in Chrome Windows. (Issue: 158931)
  • Fixed F4 inside <input type=time> should not open calendar picker. (Issue: 158482)
  • Fixed calendar picker can flicker when opened from the suggestion picker. (Issue 158608)

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

5 comments:

Philip Pham said...

ohh very nice update. now my browser is much faster than the older.

Tobias Brentrop said...

Is there a way to reset Chrome back to default flags? I am experiencing really bad performance on most google pages (G+, Maps, Youtube, etc) and I'm not sure if that is because of some flags i tried. I'm on DEV and the sites are running fine and smooth in IE.

Archlinux said...

@Tobias Brentop, yes, you just remove those from the shortcut.

There are other possibilities as to why your Chrome is so slow (extensions, AV, slow connection, you name it). The best way to figure out whether it's internally Chrome-related is to rename the settings directory (C:\Users\\AppData\Local\Google\Chrome\User Data) and to see, if it went away.

Tobias Brentrop said...

Thanks for the info, but i don't start chrome with flags, I used "chrome://flags", so the flags are set implicitly. But now as I'm typing I remember that i can see the flags in the task manager, so maybe I try to match the --force-fieldtrials flags until this is gone.

I'll try to delete User Data, but the dir seems locked even though chrome is closed and no process is running anymore. Investigating with Process Explorer now... :/

zele said...

Come on, this memory leak is making me switch to other browser. I have few sites that auto refresh and If I leave those tabs open over night Chrome will eat all the memory.

Just open some site and keep pressing F5 and observe chrome://memory-redirect/