Oh noes! This website crashes Chrome!

[Dan]

That is sweet

[astevens54]

I thought that each tab runs as a separate process and that a misbehaving web site shouldn't crash Chrome Guess that blows that theory out of the water

[Ho0ber]

I thought that each tab runs as a separate process and that a misbehaving web site shouldn't crash Chrome Guess that blows that theory out of the water

Now, that's a misunderstanding I'm seeing all over these forums today. Please note that if it is a site's code (loads of JS or some screwy plugin) causing problems with a tab, THAT TAB will crash, leaving you with an otherwise functional system. The "bug" I have here is clearly targeted at something deeper, and because of how simple it is, I can only assume that it exists solely as a test. Going to "about:%" crashes every build of Chrome I've tried it on. I should see if I can dig into the source to find out if this is intended or not.

[Reminon]

lol i had to too, just because you said not to. lol

[Geocomb]

As far as we know, it is a beta testing FEATURE for when they need to force a full browser crash.

Actually, thats not the only beta feature to force a crash. In your browser, if you type:

about:inducebrowsercrashforrealz

It will force a full browser crash. Neat, huh? Wikipedia isn't just for searching up sex terms...