Same here; google-chrome-unstable-28.0.1485.0-195393.x86_64 on Fedora 18.

Hardest crash I've experienced on this new setup.

Just took out that tab for me in windows. Seems like something else is probably going on for you.

Chromium has been a little dodgy for me lately too. Lots of memory leaks and what not. I've had to kill it's parent process id on a number of occasions (but even then, there's no reason why a browser should take out the whole OS).

They are also not really visibly working on issues like these: http://code.google.com/p/chromium/issues/detail?id=222558 http://code.google.com/p/chromium/issues/detail?id=134837

Basically, each font in each size uses some handles in a renderer. At 10000 handles, the tab renderer dies. They have a font cache but never clear it. When enough render processes together use too many GDI handles, the whole Windows desktop breaks down.

Same here. Google has to do something with all these memory leaks.

...Or releasing their iron grip on the repo.

On Chromium 25.0.1364.160 on Ubuntu 13.04 just the running tab died.

How? Couldn't you even drop to another TTY and kill the process?

I've had problems with fglrx where it crashes because you resize the window too quickly, and then it's done something really funky, so when you do CTRL+ALT+F_N it doesn't actually give you a shell.

I'd bet money OP didn't even try or doesnt know how to do that.

This is what I thought to.

I've never once had an application in Linux crash the whole OS - or at least not so long as I've had physical access to the machine (I've had rouge database requests brick a server before because it took down sshd - but that's a different story)

In fact on the laptop I'm on now, the parent link crashed Firefox. But it OOM'ed and got killed before I even noticed there was a problem (and that's on a beefy desktop environment with compositing enabled too)

You should tell your database to go easy on the rouge - a lady keeps it subtle.

This shouldn't be possible if the OS is written correctly. :-\

My bet: the OS and all the code running on it is written correctly. and you can see it gave you a warning about tainted kernel when you loaded that piece of crap nvidia/ati proprietary driver.

He's on Ubuntu. Anything is possible to make it crash.

Both of these comments are idiotic and flamebait.

And yours is very polite and contribute a lot to the discussion ;-)

but being the devils advocate here, both parents of your comment are not that far off.

Ubuntu is more prone to crash because it invites the user to install much more closed source and proprietary code, by design. so they are not that idiotic and flamebaitic.

Now that is an example of a high-quality comment! Adds value to the conversation and in no way may be considered flamebait. :-p

You would think, but I've noticed that on HN specifically, the comment pointing out that a stupid argument is forming--if it gets in early enough--tends to be both highly upvoted, and the end of the argument. One reason I like this community.

There was no argument, whether "stupid" or not. You're welcome to start one.

There already was another comment pointing out that one could kill the process from another tty.

I interpreted "Crashed my whole system" as meaning that option wasn't possible.