Hacker News Reader

Comment by myworldplz | Hacker News Reader

I've created something similar but for Firefox: http://crashfirefox.com/

Have added new crash options for users with NoScript (even if you're blocking 302s - try right clicking).

And it just keeps going, love it

    ➜  ~  curl http://crashfirefox.com/

    ....................../´¯/)
    ....................,/¯../
    .................../..../
    ............./´¯/'...'/´¯¯`·¸
    ........../'/.../..../......./¨¯\
    ........('(...´...´.... ¯~/'....')
    .........\.................'...../
    ..........''...\.......... _.·´
    ............\..............(
    ..............\.............\...
        SNITCHES GET STITCHES

    ....................../´¯/)
    ....................,/¯../
    .................../..../
    ............./´¯/'...'/´¯¯`·¸
    ........../'/.../..../......./¨¯\
    ........('(...´...´.... ¯~/'....')
    .........\.................'...../
    ..........''...\.......... _.·´
    ............\..............(
    ..............\.............\...
        SNITCHES GET STITCHES

    ....................../´¯/)
    ....................,/¯../
    .................../..../
    ............./´¯/'...'/´¯¯`·¸
    ........../'/.../..../......./¨¯\
    ........('(...´...´.... ¯~/'....')
    .........\.................'...../
    ..........''...\.......... _.·´
    ............\..............(
    ..............\.............\...
        SNITCHES GET STITCHES


    ➜  ~  curl http://crashfirefox.com | wc -l
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
    100 3613k    0 3613k    0     0  2020k      0 --:--:--  0:00:01 --:--:-- 2019k
      120000

Hah, I did the same thing, but it's not too hard to get past:

    curl -i -H 'User-Agent: Firefox' crashfirefox.com | head -n 80 | cut -b 1-100

Pushing browsers to their resource limits is fun... and makes me think that we should really have configurable limits to stop the browser consuming all RAM and crashing or affecting other applications' performance. A policy like "maximum 75% of available RAM" with a suitable cessation of further rendering when that limit is reached, with an error message, would be far better than forcing itself and all other apps into swapping and then crashing.

Hah, that click was definitely my karma for today, ty.

But the reason I posted this is because it doesn't rely on Javascript to eat up memory- anyone can post a malformed/long link to a web forum and crash the thread/site for other Chrome users immediately, without clicking thru.

Reply on news.ycombinator.com