Tuesday, March 13, 2012

Dev Channel Update

The browser hang and high CPU usage issue is fixed in 19.0.1068.1. Please check the blog post for more details.

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

  • Users of Chrome for Android who have tab sync enabled can use the “Other Devices” menu on the new tab page to open tabs from other devices.
  • Several fixes and improvements in the new Settings, Extensions, and Help pages.
  • Fixed the flashing when switched between composited and non-composited mode. [Issue: 116603]
  • Fixed stability issues 116913, 117217, 117347, 117081

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



Blogger Alen said...

Great update!!!

4:29 PM, March 13, 2012  
Blogger zcat said...

I've been waiting for android-to-desktop tab sync'ing to pop up! :) Now I finally have a good enough reason to switch from stable (17) to the dev channel. Thanks.

5:59 PM, March 13, 2012  
Blogger REO said...

Great work on the settings page! :)

6:19 PM, March 13, 2012  
Blogger Richie BINADIKA said...

Ikut menyimak artikelnya :-)


8:54 PM, March 13, 2012  
Blogger Joydou said...

Good posts, like it.

11:14 PM, March 13, 2012  
Blogger Unknown said...

This build is unusable unter arch linux 64bit.

12:33 AM, March 14, 2012  
Blogger Cliff Wakefield said...

Under OS X 10.7 and Windows 7 64bit I am getting constant hangs and very high CPU usage with this build.

Tried the usual things like disabling extensions and only loading a single page at a time, but at this point it's largely unusable and I can't seem to find a pattern to the problems.

2:30 AM, March 14, 2012  
Blogger Unknown said...

On settings page and some other website I can't scroll.

4:21 AM, March 14, 2012  
Blogger Bas said...

What Cliff Wakefield said....

Posted this using IE :S :S

6:04 AM, March 14, 2012  
Blogger Dirk Talamasca said...

I am in agreement with Cliff Wakefield and Bas. In spite of various efforts at troubleshooting and corrections 19.0.1068.0 is absolutely unusable on Win 7 64. It is a real effort just to get to the extensions and disable them and it doesn't help anyway. Attempting a search from the omnibox is a definite nail in the coffin.

Had to resort to IE to make it here.

6:29 AM, March 14, 2012  
Blogger Kurtextrem said...

dabblet.com and pages with css3 animations are resulting in a black screen for me

Win 7 x64

8:21 AM, March 14, 2012  
Blogger hIpPy said...

fyi: I'm also facing issues with Win 7 32bit. Almost unusable. It took a lot of time to open up a web page.

9:15 AM, March 14, 2012  
Blogger zedascouves said...

Count one more for unusable browser. Windows 7 x64.

9:24 AM, March 14, 2012  
Blogger Alban said...

I had the same issue with Windows 64 bit. In the end I uninstalled and when back to the stable branch. I then reinstalled the dev version and the CPU usage is now low. dabblet.com is rendering OK as well.

Win7 x64

9:26 AM, March 14, 2012  
Blogger Deric said...

Some pages I can not scroll on. Mostly pages like Chrome Settings and Extensions.

Also Chrome will not want to render/load pages when first starting up Chrome. I will have to close out Chrome then reopen Chrome so pages will load.

Everything was fine until last nights update. Hope these get fixed.

9:39 AM, March 14, 2012  
Blogger Deric said...

Oh I am also running Windows 7 64 bit.

9:40 AM, March 14, 2012  
Blogger Unknown said...

Yeah, this completely dies in Win7. Time to waste a big chunk of my day fixing this.

CSS3 transform fails, HTML5 video fails, and now this...

Firefox is looking better and better every day.

10:00 AM, March 14, 2012  
Blogger dragonGOD8 said...

I'm in XP SP3 and I've also had more than a handful of hangs and high-cpu usage since the update.

10:16 AM, March 14, 2012  
Blogger ChromeFan said...

No problem here. Windows 7 SP1,64 bit

10:24 AM, March 14, 2012  
Blogger Deric said...

@ Unknown

To be fair, you can always switch to beta or stable builds if dev builds are too chaotic for you.

10:51 AM, March 14, 2012  
Blogger Niebylski said...

Lots of problems with Win7-64 build here:
In particular: Crashes for Google Talk plugin, and Evernote Clipper.
As others have mentioned above - pages just hang indefinitely (Gmail, and others w/ and w/o Flash)

11:36 AM, March 14, 2012  
Blogger Abraham Williams said...

Constantly having the CPU maxed out with Chrome being unresponsive. OSX 10.7.3.

2:50 PM, March 14, 2012  
Blogger Benni said...

Unusable on Win7 x64.

4:57 PM, March 14, 2012  
Blogger Abraham Williams said...

If you are having issues with the CPU maxing out please star the open bug report: http://code.google.com/p/chromium/issues/detail?id=118251

5:09 PM, March 14, 2012  
Blogger Observer said...

Crashes, hangs, unstable to the MAX
Win 7 64 bit user the system becomes unresponsive

Also somehow it works in incognito mode which is a bypass in the meantime
Sometimes flash application destroys ALL chrome tabs.

5:19 PM, March 14, 2012  
Blogger Hugo said...

I don't have any problem. Windows 7 SP1, 64 bits

5:25 PM, March 14, 2012  
Blogger Dreamer said...

Unusable on Win7 x86.

(Slow boot, slow to load pages in flash, crash, crash and still in the window management crashed tabs, crashes too.)

5:43 PM, March 14, 2012  
Blogger Chromium4Life said...

Same as everyone else, can't load web pages and the CPU spikes like crazy on Win7 32bit. Had to resort to IE9 to make it on here.

9:05 PM, March 14, 2012  
Blogger Charlie said...

Not to repeat what everyone else is saying, but I am also experiencing problems with this release. Browser is completely unresponsive after opening and the only for it to quit using CPU time is to end process in the task manager.

10:34 PM, March 14, 2012  
Blogger Вова said...

Unusable for me too.

10:50 PM, March 14, 2012  
Blogger Unknown said...

Chrome dev 19.0.1068.0 on W7SP1x64 here, also many pages completely hang the browser either for ~30 seconds or forever. Gmail is one, and so is the Chromium blog.

Going to about:plugins and disabling the Flash plugin fixed it for me (for now), but obviously this is a poor idea going forward. Or is it? Hmmmm..

11:17 PM, March 14, 2012  
Blogger Unknown said...

Never mind that, I just had it happen again on Gmail even though I've disabled Flash. So disabling Flash doesn't seem to help after all.

11:33 PM, March 14, 2012  
Blogger Claus said...

Stalls on my WinXP machines, too. Consumes entire power of one core when trying to access a page. Renders fine and quickly when data are coming in but nearly times out on it's way there.

2:13 AM, March 15, 2012  
Blogger Marcin Dzikowski said...

Unusable on W7 x64. Had to switch to FF :( Omnibox not working. Gmail is hanging or not refreshing. Disaster :(

2:29 AM, March 15, 2012  
Blogger DopedAngel said...

Like everyone else is saying chrome is unusable on Win 7 32bit and 64bit pages don't load.
Am using firefox to post here. I know its a problem with this version as I am having the same problem at home and work. With different networks and OS.

3:06 AM, March 15, 2012  
Blogger stoinov said...

My experience is that I was able to use it without any issues until I installed the latest windows updates from March 13. After that I also got the 100% CPU usage.
After disabling flash I was able to alleviate the constant load and now I only get sporadic spikes when I interact with the pages.

So as a temp workaround you could try disabling the flash in chrome://plugins/

4:34 AM, March 15, 2012  
Blogger Yoav said...

Same problem here.
Had to open incognito to post this.

4:50 AM, March 15, 2012  
Blogger Vinh Aor said...

Please fix these problem as soon as possible

6:21 AM, March 15, 2012  
Blogger Macabu said...

Freezes at 15~30s after opening the browser. Latest Dev release, Windows x64 SP1, same problem as everyone, disabled plugins, flags and nothing seemed to fix :/
Using Firefox to write this message *LOL*

6:41 AM, March 15, 2012  
Blogger xinaesthete said...

I know that many comments are already stating the same thing or very similar, but it is totally unusable here under Win7 64bit.

It possibly went from bad to FUBAR in correlation with some Windows update, but I'm not sure exactly how the different updates relate.

8:25 AM, March 15, 2012  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home