CrashFirefox.com

by moloch • 11 years ago

21 28 11 years ago

skidoo• 11 years ago

Well that's just mean.

DigitalSea• 11 years ago

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.

cozzyd3• 11 years ago

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

windlep4• 11 years ago

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.

pki• 11 years ago

The title is named crash firefox isn't it?

windlep4• 11 years ago

Yes, it's not named "lock-up the entire system". I was expecting a segfault, quite disappointed.

newsvatore• 11 years ago

There was at least one clue provided by the name of the site...

windlep4• 11 years ago

A crash is not a hang. Firefox never crashed, eventually linux asked if I wanted to kill it, but there was no segfault, no crash.

andrewchambers• 11 years ago

I don't know what you expected.

M8• 11 years ago

A big label on the page saying "Not really, FF is rock-solid. Have a nice day HN!"?

cozzyd3• 11 years ago

I just sshed into my computer from my phone to kill firefox, although I probably could have switched to a VT as well.

windlep4• 11 years ago

I continue to be incredibly sad that any OS considers it ok to lock-up the entire UX for a program running amok. Most people would consider such an OS defective, and consider what else is out there, rather than ssh into it. I can't really fault them, I do wonder what is wrong with people making such systems that think this is an acceptable situation.

mijoharas• 11 years ago

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

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

malkia• 11 years ago

Got a crash on Chrome (Linux)

majke• 11 years ago

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

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

TheLoneWolfling2• 11 years ago

It breaks things, so it's an issue.

It may not be one that they intend to fix, but it's still an issue regardless.

tomohawk• 11 years ago

My firefox with noscript did not crash

zcid• 11 years ago

Hmm, I haven't checked the code yet, but Firefox 37 on Arch with NoScript crashed for me on a reload. I just got the noscript detection the first time.

TheLoneWolfling2• 11 years ago

Ditto.

It did hang for a bit (30s?) when closing the tab, however.

rsuelzer2• 11 years ago

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. :)

rsuelzer2• 11 years ago

If anyone cares, here is a screen shot of the result on nightly build. http://imgur.com/j0T7Fjh

minot• 11 years ago

This is what I got... https://i.imgur.com/wZAfZhN.png

nunsncustard• 11 years ago

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

Mizza• 11 years ago

Hung, but eventually recovered on 37.

Not really sure what I was expecting.

Manishearth• 11 years ago

Context: https://bugzilla.mozilla.org/show_bug.cgi?id=1105796

thyrsus• 11 years ago

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.

soylentcola• 11 years ago

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

Did indeed crash Firefox 37.0.1.

CrashFirefox.com

Related Stories