Dev Channel Update: 3.0.187.0
Wednesday, June 10, 2009 | 18:28
Labels: Dev updates
Note: This release has been stopped. The browser crashes whenever you click on a menu item. We'll be releasing a fix later today. [mal, 11 June 2009]
Google Chrome 3.0.187.0 has been released to the Dev channel for Windows, Mac OS X, and Linux.
Highlights for this release:
- Linux: Import passwords from Firefox. (Issue: 11191)
- On Mac use Keychain for passwords. (Issue: 11745)
- Fix regression where Omnibox would drop characters during rapid typing. (Issue: 13428)
- The web inspector is now working again. (Issue 13411)
- Fix browser hang due to plugin deadlock. (Issue: 12624)
- --enable-user-scripts is working again. (Issue 13290)
- Clicking an extension toolstrip no longer selects the first tab. (Issue 13547)
- Extension buttons now show after install (Issue 13609)
- Increase the maximum number of cookies to 3000. This matches Firefox. (Issue: 8850)
- When the contents don't have title, use URL for the name of bookmark entry. (Issue: 5965)
- Move download shelf from per-tab to per-window. (Issue: 9025)
- Improved support for Squid proxies. (Issue: 8771)
- Fixes a flash plugin hang on Google Finance ticker symbols in a background tab. (Issue: 12993)
Version Changes:
- V8 - 1.2.7
You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel.
If you find new issues, please let us know by filing a bug athttp://code.google.com/p/chromium/issues/entry.
Jonathan Conradt
Engineering Program Manager
74 comments:
Milorad said...
a lot of crashes expecially when i go to prefences
6:38 PM, June 10, 2009
Fernando said...
Same here.... Impossible to use this (using IE8 while waiting a new version)....
6:47 PM, June 10, 2009
Red said...
This is a very bad release, worse than the last one! Chrome crashes when you try to do anything from the "Tools" icon. Just like the 2 above, have to use another brwoser to comment...
So how do I update when going to "About Google Chrome" crashes Chrome?!
6:57 PM, June 10, 2009
darrenew said...
Thank goodness i am not the only one with this problem! Like said above, pretty much any thing you try to open in the tools menu like history,downloads,about,ect..causes chrome to crash!
7:25 PM, June 10, 2009
San said...
Logmein doens't work
7:25 PM, June 10, 2009
San said...
Crashes when you open anything from the menu even like incognito mode.
7:26 PM, June 10, 2009
Mark Larson (Google) said...
The crash is http://code.google.com/p/chromium/issues/detail?id=13759.
I'm stopping the update of this build. Apologies to those who've already got the update.
We'll push a fix as soon as we can tomorrow.
7:31 PM, June 10, 2009
Jim said...
As noted above, basically a nonfunctional build. Crashes when attempting to open any menu, even the About menu. How did this get out the door?
7:33 PM, June 10, 2009
leyland said...
7:41 PM, June 10, 2009
Ricardo A. said...
In addition to the crashes the browser also seems slower.
Does anyone felt that?
8:04 PM, June 10, 2009
San said...
Thanks Mark for such a prompt response.
8:09 PM, June 10, 2009
SHAWN said...
Except for the crashing when checking the version or bookmarks, this release is SUPER FAST!!! Thanks for reacting so quick to the issues in this release.
8:38 PM, June 10, 2009
Revanth said...
Not having any of the crash issues others have mentioned. This is a very solid build, especially over the last 183.1, and thankful user scripts got fixed again.
While the cookie count was increased to 3000, when will you give us the ability to block specific cookies like all the other browsers do?
8:53 PM, June 10, 2009
SHAWN said...
Question -- since the browser crashes when we check the version number, how will we be able to click the update button when the next version is released?
9:31 PM, June 10, 2009
pkasting said...
@Jim: Dev channel releases get significantly less testing. That low overhead is part of how we can manage to release as frequently as once per week. If you're not prepared to have occasional awful results, the beta channel is probably better for you.
@SHAWN: You don't need to force manual update checks in order for things to update, that just makes it happen sooner.
10:11 PM, June 10, 2009
Móricz Csaba said...
dev channel update: 3.0.187.0
preference and abaut goole crome bad
az új fissítés után nem muxik a személyre szabás. a "crhome lefagy"
:-(
10:44 PM, June 10, 2009
Fabio_Rulez said...
ok, google crash when you try to go on the options, but there is a new very important feature that you guys have not notice yet, the dowload is per window and not per tab, and when you try to close the browser with a download open a message box appears warning you. this is good. i hope a day will be possible to download something even closing the window, like in IE. but this is a good thing anyway
12:06 AM, June 11, 2009
Craig said...
chrome crashes when i go to options or anything on the menu bar > reverting back
very bad release
12:54 AM, June 11, 2009
aaron said...
Can do literally anything from the tools menu without the browser crashing.. weird.
1:30 AM, June 11, 2009
Elektra said...
Crash when i go to Prefs.
Rus/WinXP pro Sp3
2:46 AM, June 11, 2009
Slaine said...
Version seems snappy, love the new changes.
i agree with Fabio_Rulez would be nice if when the window is closed there is a way to keep the downloads going.
Extension system fixes this version has fixed the problems i had with the last release, good work there.
3:00 AM, June 11, 2009
Slaine said...
Also worth noting that when i restore after crash with, it crashes after a few seconds loading the tabs.
I experienced this after the tools bug, i had about 6 tabs open
3:06 AM, June 11, 2009
Krzysztof said...
There is also a bug with flash games. While loading the browser hangs.
3:08 AM, June 11, 2009
Antonio said...
Bad release! Very bad! With W7 it's impossible to click on tools buttons. Otherwise I think this release is the fastest I ever tried.
Hope fix this soon! I can't wait tomorrow! I use/love just Chrome! T_T :(
3:31 AM, June 11, 2009
black said...
how am I suppose to update if chrome crashes immediately after clicking the wrench? man this was a fail update
5:28 AM, June 11, 2009
San said...
Revanth said...
Not having any of the crash issues others have mentioned.
What OS are you using?
Thanks
5:43 AM, June 11, 2009
Dre said...
Just got the update today and I'm getting crashes when clicking on the tools menu.
5:46 AM, June 11, 2009
andre said...
I see the google finance crash (12993) has been fixed. Thank you dev-team. This was quick. ;)
6:14 AM, June 11, 2009
තමීර said...
How can I update when this bug is fixed? Coz accessing About Google Chrome is not possible. Any method I can revert back to the old version?
6:21 AM, June 11, 2009
Wolfgang said...
Any ETA for a hotfix?
6:27 AM, June 11, 2009
Meok said...
For those who are having problems, I suggest you do as I did. Uninstall Chrome but leave the browsing data intact. Re-install the stable version and it will keep your bookmarks, homepage, search-engines etc. Use that build until the next dev build is released.
6:32 AM, June 11, 2009
Tomo said...
I didn't get any crash with new release... Task manager is working, fonts in omnibar are improved, it's slightly faster then previous release.
p.s.: I'm using it for 30 minutes :)
6:45 AM, June 11, 2009
Cakalaky said...
Mine crashes everytime I go to preferences or anything. Not worth the update. Unusable. :(
6:55 AM, June 11, 2009
Tomo said...
Did you update from previous version of Google Chrome or "clean install"? Try to clear personal data, it might help :)
6:58 AM, June 11, 2009
Brian Sullivan said...
It seems this update was not pulled as suggested earlier -- I got the update this morning.
7:00 AM, June 11, 2009
doekman said...
It would be nice if some more info was given on what was changed with the new v8 release. After some research, I found this link:
http://src.chromium.org/viewvc/chrome?view=rev&revision=17852
Further: I'm not sure I like the new download-sidebar behaviour. Before, each tab had it's own download items, and the download-window showed all downloads done within chrome.
7:11 AM, June 11, 2009
jasper2005 said...
dont download this latest yet as it does crashes alot!!
using ie8 until it fix!!!
7:11 AM, June 11, 2009
francois said...
The version 3.0.187.0 (June 10, 2009) are a merde (shit).
Google Chrome is unusable. a lot of dysfunctions
7:20 AM, June 11, 2009
Wolfgang said...
Got the update an hour ago, and it wish it had been pulled from the servers :(
7:27 AM, June 11, 2009
shiba said...
Hey everyone! Just clam down. Remember that this is a Dev Channel Update? If stable Chrome wanted, please go back to Stable Channel
7:27 AM, June 11, 2009
Wolfgang said...
@shiba: sure, but if a version (even an alpha or dev version) is already known to cause major problems, why still continue distributing it?!?
7:31 AM, June 11, 2009
Brandon Singer said...
Crashes like crazy for me too. But it is the dev channel. I'll just be limited in what I can do until the new build.
I'll just be using FF more today.
8:05 AM, June 11, 2009
Swordfish said...
A WARNING IN THE UPDATE POST WOULD HAVE BEEN NICE. don't understand why you haven't done that.
8:23 AM, June 11, 2009
Nolan said...
No animation for the Home button while hovering or clicking in this version.
8:28 AM, June 11, 2009
Stephanie said...
Anything in the tools or page buttons crashes. The resut is the same in Vista and Windows 7.
First time I have seen such a sloppy release
8:38 AM, June 11, 2009
krtulmay said...
As another poster mentioned, a warning about all the menus crashing would have been nice!
What's happened to the known issues part of the posting?
8:51 AM, June 11, 2009
joesixgig said...
For this reason I switch back to the stable channel after every Dev update, and only go back to the Dev channel after I scan the comments for severe bugs in new builds. Maybe a tip for those users who rely on Chrome as their main browser. -Joe
8:54 AM, June 11, 2009
Chris said...
Crashes for me in XP SP3 when I select pretty much anything from either menu. Comments above verify that it isn't OS-specific (happening on Vista and Win7).
Ordinarily I would agree with the point made above that this is a dev release and that we should expect a lower degree of stability, but every single option on both menus crashing the browser does make it impossible for some to use and is somewhat outside the ordinarily expected dev build quirkiness. Chrome dev builds have until now been of amazingly good quality. I'm using Firefox for today and hoping for the fix for this to happen tomorrow.
9:15 AM, June 11, 2009
Alexi said...
Well.. yeah. It keeps crashing. I don't like it. Neither do you. I guess. So I solve this problem by... uninstalling Google Chrome and installing so it's stable by default. Now I'm using stable. When there's new release of Dev Channel, then I will come back to it.
9:17 AM, June 11, 2009
Kate said...
Same problem here with crashing when the Tools Menu is selected. Uninstall, reinstall and back to the Beta channel until the next release ;)
9:31 AM, June 11, 2009
Arek said...
This dev release is in beta channel now!
9:41 AM, June 11, 2009
houtxone said...
Yeh, you guys really out did yourselves this time with the latest development release but we still love ya. Please fix it soon.
Thanks
9:57 AM, June 11, 2009
Zzz said...
a lot of crashes when open options, about Google chrome, report bugs....
10:35 AM, June 11, 2009
Justino.Mora@elegibles.com said...
Just because you guys have a weekly target, You DO NOT HAVE to release SCRAP. Come on....
11:23 AM, June 11, 2009
LC said...
It crashes when I clicked on the menus...BAD!!
11:51 AM, June 11, 2009
Patrick said...
Everyone stop complaining and whining. This release is in the Dev channel for a reason. If you don't like the risk of a broken release please subscribe to the beta/stable channels. In a way you brought this upon yourselves.
12:29 PM, June 11, 2009
luxiano said...
Although this dev version crash when you click on any menu, the browser it's still usable, no need to switch to another browser just for comment... I'm using this dev version to comment.
1:05 PM, June 11, 2009
David said...
I'm actually having no problems with this build. I don't get any of the crashes everyone's been talking about. I wonder why...
1:27 PM, June 11, 2009
Robbie said...
I changed the DEV Channel to beta to get more stable and YET is stuck with this version no matter how many times I'll reinstall (Vista). I'm myself is a dev, do I have to swipe off all chrome disk files, reg keys or what's the problem with the install? Why am I not getting earlier versions via Dev Channel??
this is an awful release and should be killed from the server. HELP
1:35 PM, June 11, 2009
San said...
What OS you are using David?
1:35 PM, June 11, 2009
San said...
Robbie, Just uninstall it from the Control panel, Keep user files.
Then go to Google Chrome download page and at the bottom there's a link "Try beta" and directly download the latest beta version.
1:36 PM, June 11, 2009
Robbie said...
San, thanks, that worked. Sady the channel changer won't change anything, a full uninstall has to be done (no need to delete the user data folder data).
Here's a SUPER tips to the Chrome Test Team, ALWAYS make sure that the autoupdate feature works BEFORE releasing on a release server.
1:50 PM, June 11, 2009
black said...
still nothing has been fixed, my browser is constantly crashing.
youtube videos(flash) is also worse than before. It has always given me problems on chrome but now they won't even load.
I'm starting to think I should try to revert back to use firefox. It's so hard to switch back after getting used to chrome tho! gah
2:21 PM, June 11, 2009
San said...
It would be nice to know what OS Google team Uses?
I am on WinXP x64.
Thanks
2:23 PM, June 11, 2009
brad said...
@black, don't use Dev Channel releases if you can't stand instability. Go back to the Beta or Stable Channel.
2:28 PM, June 11, 2009
Justino.Mora@elegibles.com said...
No one expects instability and crashes on regular items already tested and delivered.
One may expect instability and crashes on new things and functions but not on old regular parameters like the menu.
Releasing for the sake of releasing is generating bad image.
2:56 PM, June 11, 2009
Leonardo said...
two BIG problems...
#1 crashes when selecting anything in tools and page settings!
#2 download speed for downloads is still missing both in the bar and on the download's page
Both problems are being experienced on Windows 7 32bit build 7201!
PLZ FIX!!!
2:59 PM, June 11, 2009
Smarty said...
crashes when I click the right button on the tab =\
3:14 PM, June 11, 2009
PLUMO said...
SERIAL CRASHES!!!!!!!
4:26 PM, June 11, 2009
Fabio Turati said...
To all those that are whining about this problem: it is obvious that the guy who introduced it didn't notice it. Do you remember version 2.0.176.0? It was ready to be released, there were also release notes. But in the end it was cancelled, because it was unstable. If the devs had noticed this problem, they would have CERTAINLY stopped it.
Do you think the devs like being insulted by a lot of people who don't even understand what "Dev channel" means? Do you think they were happy to deal with something like 42 (FORTY-TWO!!!) duplicates of issue 13759? Do you really think it is so damn easy to avoid regressions and to setup a perfect testing procedure?
There have been problems, yes:
1) The bug wasn't found: well, they've already taken care (read release notes for 187.1)
2) The release of this version was stopped, according to Mark Larson, but nevertheless I was able to get it some hours after his post, as well as many others, which probably means the stopping procedure has issues. In case, they have certainly noticed, and I'd bet that in the future they will test this specifically, by releasing another version and then stopping it.
I agree that this release was a bad one, and like many others I was surprised that such an evident bug slipped through.
So what??
THESE THINGS HAPPEN, full stop. It's the price to pay for being curious and getting new features very early. As many others have said, those who are not willing to take this risk should revert to beta.
Moreover, I'd like to point out that every time there has been a seriouos or annoying bug, it has been fixed very quickly with a special release. It happened for the shrinking tabs around version 156; it happened for the new tab without focus on omnibox (version 168); it happened for the small non-english fonts with version 182. And it has happened now. This means that being on the dev channel implies facing occasional small problems that get fixed very quickly. If you don't accept that, go back to beta.
By the way, the browser was still usable: the menu was broken, but shortcuts (for example, CTRL+B for bookmarks) worked.
Sorry for writing such a long post.
4:59 PM, June 11, 2009
Robbie said...
I agree with the dev. about this is a beta channel, don't use it if you can't take it.
But at the same time YOU have as developer make sure not to mess upp update pakages/release channels.
Don't release for the release itself, always make sure the update is reversible.
6:52 AM, June 12, 2009
Terry said...
Just curious. Do y'all use automated regression testing? If so, how much code coverage do you get from them?
5:05 PM, June 14, 2009
Andrés Parada said...
youtube is worthless on this dev channel...I'm just forced to switch to firefox every time I want to load a video!
7:18 PM, June 14, 2009
Linux_is_next said...
Give up.. I feel that if google makes a webbrowser - what in the world why? it feels creepy because of google can order the developer team to find out what people search on. you can get a 1984 around the clock.
6:58 PM, June 15, 2009
Post a Comment