5 ms·
I wish I had read that first :/ Crashed my whole system Chromium 25.0.1364.160 Ubuntu 12.04
by tomwalker 13y ago
I wish I had read that first :/
Crashed my whole system
Chromium 25.0.1364.160 Ubuntu 12.04
- itistoday2 13y agoThis shouldn't be possible if the OS is written correctly. :-\
- drmr 13y agoHe's on Ubuntu. Anything is possible to make it crash.
- OGC 13y agoBoth of these comments are idiotic and flamebait.
- itistoday2 13y agoNow that is an example of a high-quality comment! Adds value to the conversation and in no way may be considered flamebait. :-p
- derefr 13y agoYou 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.
- itistoday2 13y agoThere was no argument, whether "stupid" or not. You're welcome to start one.
- OGC 13y agoThere already was another comment pointing out that one could kill the process from another tty.
- itistoday2 13y agoI interpreted "Crashed my whole system" as meaning that option wasn't possible.
- gcb0 13y agoAnd 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.
- gcb0 13y agoMy 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.
- laumars 13y agoHow? Couldn't you even drop to another TTY and kill the process?
- OGC 13y agoI'd bet money OP didn't even try or doesnt know how to do that.
- laumars 13y agoThis 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)
- nkozyra 13y agoYou should tell your database to go easy on the rouge - a lady keeps it subtle.
- hdevalence 13y agoI'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.
- jlgreco 13y agoJust took out that tab for me in windows. Seems like something else is probably going on for you.
- laumars 13y agoChromium 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).
- isalmon 13y agoSame here. Google has to do something with all these memory leaks.
- gcb0 13y ago...Or releasing their iron grip on the repo.
- atesti 13y agoThey 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=222558 http://code.google.com/p/chromium/issues/detail?id=134837 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.
- ironcladlou 13y agoSame here; google-chrome-unstable-28.0.1485.0-195393.x86_64 on Fedora 18. Hardest crash I've experienced on this new setup.
- mickt 13y agoOn Chromium 25.0.1364.160 on Ubuntu 13.04 just the running tab died.