And because of why that crashes happened?
Nothing wierd about the Dev channel?
This of course raises the question, is there any way to roll back once you have upgraded?
@//M: See http://dev.chromium.org/getting-involved/dev-channelChrome 220.127.116.11 will come later today or tomorrow
Is there some sensible reason, not including alcohol and drugs, why 172.5 that is numerically smaller than 173.1 was actually released after 173.1? ;-)
Google Chrome 18.104.22.168 is already there!
Is there some sensible reason, not including alcohol and drugs, why 172.5 that is numerically smaller than 173.1 was actually released after 173.1? ;-)Yes, there is -- you are mixing up the release numbers for the Dev channel and the Beta channel.
If you look closely 173.1 is the dev channel172.6 is Beta ...
Slip of the fingersThat should be 172.5
I had crashes with 172.5, but now also with 172.6. GMail only, but it seems to be because of some user scripts that worked fine with the previous version...
Anyone else experiencing 172.6 to be responding somewhat slower? When I click on a link on the Most Visited tab or when I enter an URL and hit enter, there is a half second long delay before anything gets loaded. Don't know if there actually is a delay or if things have already started happening in the background, but there sure is a short delay before there is any visible response.Is this just me, or can anyone confirm?
I can't say that I have noticed any delay with this release.
Over here this release is behaving more and more bad. It (sometimes) forgets to load pages. Have to close tab and open new one to get it running again. It hangs when trying to run Shockwave plugins. It at times refuses to shut down, and I have to kill Chrome through the task manager.All in all, it's the worst release I've been running so far, since I first joined the beta channel in December.
Post a Comment