from Hacker News

CrashFirefox.com

by moloch on 4/10/15, 12:49 AM with 28 comments

  • by tomohawk on 4/10/15, 1:53 AM

    My firefox with noscript did not crash

  • by majke on 4/10/15, 1:53 AM

    Not a bug! The crash is as intended! (at least in chrome)

    https://code.google.com/p/chromium/issues/detail?id=432559

  • by rsuelzer on 4/10/15, 1:58 AM

    Actually, it didn't crash my firefox 40.0a . It asked me eventually if I would like to stop running scripts on this page. Which I did and I am now typing this using the same Firefox instance. Only it now is using 4.6gb of memory. :)

  • by thyrsus on 4/10/15, 8:35 AM

    When it detected noscript, it replaced the page with this:

        <meta http-equiv="refresh" content="0">AAAA.........
    ...as displayed with ^U, except the "AAAA...." wasn't visible until I pasted it in this text box. I'm not sure, but I suspect the length of the AAAAs was growing rapidly. There's a lot of memory and more than one core on this system, so I think I killed the tab, which appeared only as a blank page, before it became too destructive.

  • by DigitalSea on 4/10/15, 1:41 AM

    As a Firefox user I can confirm this does indeed crash Firefox. It however also crashes Chrome to an extent (at least on Windows) you get the aw snap page shortly after it loads.

    Seems like it just overloads the browser using this technique in the URL: data:text/html,<script>location+=location+'A'.repeat(100000000);</script> - I haven't tested in any other browser, but to me that technique would crash any browser, probably even worse on mobile.

  • by Manishearth on 4/10/15, 7:47 AM

  • by nunsncustard on 4/10/15, 3:04 AM

    Try running 'curl' on that URL (NQSFW). You can see what it's doing with the loop majke pointed out.

  • by cozzyd on 4/10/15, 1:42 AM

    Hmm, it started using a bunch of CPU and memory, but I kill -9ed it before it actually died by itself.

  • by soylentcola on 4/10/15, 4:25 PM

    It was like knowing the link is a Rickroll and clicking on it anyway...

    Did indeed crash Firefox 37.0.1.

  • by windlep on 4/10/15, 1:42 AM

    Seriously, no disclaimer that this will hang Firefox, and will likely lock up a system for 20+ seconds before it will let you kill Firefox (linux)? (Thankfully I run linux in a vmware image, so I can go play a game while waiting for linux to figure out the process went rogue)

    I didn't realize HN was the new 4chan/8chan. Sigh.

  • by malkia on 4/10/15, 1:52 AM

    Got a crash on Chrome (Linux)

  • by mijoharas on 4/10/15, 1:43 AM

    content in case it crashes your browser and you're interested:

        data:text/html,<script>location+=location+'A'.repeat(100000000);</script>

  • by Mizza on 4/10/15, 4:50 AM

    Hung, but eventually recovered on 37.

    Not really sure what I was expecting.

  • by skidoo on 4/10/15, 1:39 AM

    Well that's just mean.