Cool, I just added a link to this blog into my blog. Very interesting.
Michael Adams
· 1 year ago
Nice!
Funny how sometimes the simplest bugs slip through the testing process.
It also shows the limits of the isolation between tabs. The whole Chrome application crashed taking down all the tabs I had open, even one I pulled out of the original window to stand alone in its own window.
[...] Sarathc blog points out you can crash Chrome simply by typing :% in the Chrome [...]
smot
· 1 year ago
This has been fixed in Version 0.2.149.29 (1798)
Developer Tools available with
· 1 year ago
[...] not giving an update notification like Mozilla. That’s really bad. I know it only when a guy commented for my previous post on Chrome bugs. He was talking, that the “:%” with Chrome has been [...]
emimer
· 11 months ago
also try to type something starting with tr get another chrome crash
Rob
· 10 months ago
so we know why chrome crashes....... Is google doing something about it? Wisecracks have any solution? Geeshhhh.!
swordfish1987
· 7 months ago
Hey its fixed....I am using version 2.0.172.30...there are no issues.. and by the way its still a beta..there is no reason to make fun of such minor glitches..afterall its google.. they know what they are doing...
All Comments
Funny how sometimes the simplest bugs slip through the testing process.
It also shows the limits of the isolation between tabs. The whole Chrome application crashed taking down all the tabs I had open, even one I pulled out of the original window to stand alone in its own window.
I'm going to add a link on my blog as well.
Michael Adams
www.chromevoice.com
get another chrome crash
and by the way its still a beta..there is no reason to make fun of such minor glitches..afterall its google..
they know what they are doing...