Not a bug! The crash is as intended! (at least in chrome)<p><a href="https://code.google.com/p/chromium/issues/detail?id=432559" rel="nofollow">https://code.google.com/p/chromium/issues/detail?id=432559</a>
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. :)
When it detected noscript, it replaced the page with this:<p><pre><code> <meta http-equiv="refresh" content="0">AAAA.........
</code></pre>
...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.
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.<p>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.
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)<p>I didn't realize HN was the new 4chan/8chan. Sigh.
content in case it crashes your browser and you're interested:<p><pre><code> data:text/html,<script>location+=location+'A'.repeat(100000000);</script></code></pre>