Thursday, February 6, 2014

Dev Channel Update

The Dev Channel has been updated to 34.0.1825.4 for Windows, Mac, and Linux.

This release fixes a number of crashes and other bugs. A full list of changes is available in the SVN log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Daniel Xie
Google Chrome

Labels:

17 Comments:

Blogger Spouby said...

昨天刚更新完今天又更新,我大版本帝威武!

8:52 AM, February 06, 2014  
Blogger usaff22 said...

It was updated yesterday - wow!

1:57 PM, February 06, 2014  
Blogger Kevin Fiebig said...

Did aura on linux get disabled on purpose? Or is it just broken this build?

5:44 PM, February 06, 2014  
Blogger Online Typecursus said...

When will this version will go live?

2:01 AM, February 07, 2014  
Blogger Kenneth said...

Worst release ever! :-)

Tabs randomly taking a full cpu. Issue 341461 & 341515. First time I'm considering going back to Beta.

3:52 AM, February 07, 2014  
Blogger Tambosi said...

High cpu use with some tabs, randomly (in my case Yahoo mail, Feedly). Please fix it ASAP.

5:42 AM, February 07, 2014  
Blogger Jacob Groß said...

Also this build broke Adblock (both).

9:19 AM, February 07, 2014  
Blogger Nash said...

So now we have to choose between an unstable release and a walled-garden release (beta)...

Maybe I should go back to Firefox or Opera.

4:17 AM, February 08, 2014  
Blogger dhtuuu said...

Nash what do you mean with "walled garden release" about beta ?

7:50 AM, February 08, 2014  
Blogger Nash said...

@dhtuuu

The latest beta will disable extensions that it considers suspicious. All third-party extensions and extensions not on the Chrome web-store are disabled and in many cases cannot be enabled even manually.

Google Devs on the mailing list suggests (read enforce) all third-party extension developers to move to the Chrome Webstore.

This is literally BS we expect from Apple, not Google.

11:52 AM, February 08, 2014  
Blogger Nuno Peralta said...

@Nash
That's very good if Chrome is *finally* disabling suspicious/malicious extensions. Several users report that my site is not working properly for them, and it begins working well when they remove some "toolbar" extension or crap like that. Unfortunately, the only way I have to test my site against some extension like that is to install the virus program myself. Sometimes I can't even know where's that f****** virus I can download to test in a virtual machine...

3:34 PM, February 08, 2014  
Blogger Kevin Fiebig said...

On top of aura getting broken in linux. The latest chrome dev build decided it was going to forget about ~/.config/google-chrome-unstable/default/ and store all of its user data in ~/ ...pic http://i.imgur.com/LUUrXAr.png

4:39 AM, February 09, 2014  
Blogger Nash said...

@Nuno Peralta
The problem is not that it is disabling suspicious extensions, but with the definition. It is also disabling any extensions that are not on the Google Web Store. And the most important problem is that it is not providing a way to re-enable the extensions that have been disabled.

1:53 AM, February 10, 2014  
Blogger Zarko Hristovski said...

It really blows up my CPU. Win 8.1 Pro, 64bit, 8 GB RAM.

2:16 AM, February 11, 2014  
Blogger usaff22 said...

@Kevin Fiebig

What OS/theme is that? looks great

9:25 AM, February 11, 2014  
Blogger Seth Roby said...

Some tabs, especially (but not only) those with ties to Youtube (shocker, another Google run site) e.g. embed videos, downloading sites, and YouTube itself, will use massive amount of CPU power and RAM. Having Facebook and one other tab open put chrome's total memory usage at well over 600,000 kb and had my dual cores at 100% power.

6:13 PM, February 11, 2014  
Blogger Kevin Fiebig said...

@usaf22

I use arch with cinammon2, but you don't see that. What you are seeing is just numix gtk. Link below.

http://satya164.deviantart.com/art/Numix-GTK3-theme-360223962

8:59 AM, February 13, 2014  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home