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]
a lot of crashes expecially when i go to prefences
Same here.... Impossible to use this (using IE8 while waiting a new version)....
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?!
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!
Logmein doens't work
Crashes when you open anything from the menu even like incognito mode.
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.
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?
In addition to the crashes the browser also seems slower.Does anyone felt that?
Thanks Mark for such a prompt response.
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.
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?
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?
@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.
dev channel update: 184.108.40.206preference and abaut goole crome badaz új fissítés után nem muxik a személyre szabás. a "crhome lefagy":-(
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
chrome crashes when i go to options or anything on the menu bar > reverting backvery bad release
Can do literally anything from the tools menu without the browser crashing.. weird.
Crash when i go to Prefs.Rus/WinXP pro Sp3
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.
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
There is also a bug with flash games. While loading the browser hangs.
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 :(
how am I suppose to update if chrome crashes immediately after clicking the wrench? man this was a fail update
Revanth said...Not having any of the crash issues others have mentioned.What OS are you using?Thanks
Just got the update today and I'm getting crashes when clicking on the tools menu.
I see the google finance crash (12993) has been fixed. Thank you dev-team. This was quick. ;)
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?
Any ETA for a hotfix?
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.
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 :)
Mine crashes everytime I go to preferences or anything. Not worth the update. Unusable. :(
Did you update from previous version of Google Chrome or "clean install"? Try to clear personal data, it might help :)
It seems this update was not pulled as suggested earlier -- I got the update this morning.
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=17852Further: 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.
dont download this latest yet as it does crashes alot!!using ie8 until it fix!!!
The version 220.127.116.11 (June 10, 2009) are a merde (shit).Google Chrome is unusable. a lot of dysfunctions
Got the update an hour ago, and it wish it had been pulled from the servers :(
Hey everyone! Just clam down. Remember that this is a Dev Channel Update? If stable Chrome wanted, please go back to Stable Channel
@shiba: sure, but if a version (even an alpha or dev version) is already known to cause major problems, why still continue distributing it?!?
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.
A WARNING IN THE UPDATE POST WOULD HAVE BEEN NICE. don't understand why you haven't done that.
No animation for the Home button while hovering or clicking in this version.
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
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?
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
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.
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.
Same problem here with crashing when the Tools Menu is selected. Uninstall, reinstall and back to the Beta channel until the next release ;)
This dev release is in beta channel now!
Yeh, you guys really out did yourselves this time with the latest development release but we still love ya. Please fix it soon.Thanks
a lot of crashes when open options, about Google chrome, report bugs....
Just because you guys have a weekly target, You DO NOT HAVE to release SCRAP. Come on....
It crashes when I clicked on the menus...BAD!!
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.
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.
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...
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
What OS you are using David?
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.
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.
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
It would be nice to know what OS Google team Uses?I am on WinXP x64.Thanks
@black, don't use Dev Channel releases if you can't stand instability. Go back to the Beta or Stable Channel.
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.
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 pageBoth problems are being experienced on Windows 7 32bit build 7201!PLZ FIX!!!
crashes when I click the right button on the tab =\
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 18.104.22.168? 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.
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.
Just curious. Do y'all use automated regression testing? If so, how much code coverage do you get from them?
youtube is worthless on this dev channel...I'm just forced to switch to firefox every time I want to load a video!
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.
Post a Comment