CrashFirefox.com (opens in new tab)

(crashfirefox.com)

21 pointsmoloch11y ago28 comments

28 comments

27 comments · 14 top-level

windlep11y ago· 8 in thread

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.

andrewchambers11y ago

I don't know what you expected.

M811y ago

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

cozzyd11y ago

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

windlep11y 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.

1 more reply

pki11y ago

The title is named crash firefox isn't it?

windlep11y ago

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

newsvatore11y ago

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

windlep11y 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.

tomohawk11y ago· 2 in thread

My firefox with noscript did not crash

zcid11y 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.

TheLoneWolfling11y ago

Ditto.

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

rsuelzer11y ago· 2 in thread

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

rsuelzer11y ago

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

minot11y ago

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

majke11y ago· 1 in thread

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

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

TheLoneWolfling11y 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.

thyrsus11y 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.

DigitalSea11y 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.

Manishearth11y ago

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

nunsncustard11y ago

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

cozzyd11y ago

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

soylentcola11y ago

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

Did indeed crash Firefox 37.0.1.

malkia11y ago

Got a crash on Chrome (Linux)

mijoharas11y ago

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

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

1 more reply

Mizza11y ago

Hung, but eventually recovered on 37.

Not really sure what I was expecting.

skidoo11y ago

Well that's just mean.

j / k navigate · click thread line to collapse

28 comments

27 comments · 14 top-level

windlep11y ago· 8 in thread

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

andrewchambers11y ago

I don't know what you expected.

M811y ago

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

cozzyd11y ago

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

windlep11y ago

1 more reply

pki11y ago

The title is named crash firefox isn't it?

windlep11y ago

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

newsvatore11y ago

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

windlep11y 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.

tomohawk11y ago· 2 in thread

My firefox with noscript did not crash

zcid11y 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.

TheLoneWolfling11y ago

Ditto.

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

rsuelzer11y ago· 2 in thread

rsuelzer11y ago

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

minot11y ago

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

majke11y ago· 1 in thread

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

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

TheLoneWolfling11y 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.

thyrsus11y ago

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

    <meta http-equiv="refresh" content="0">AAAA.........

DigitalSea11y 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.

Manishearth11y ago

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

nunsncustard11y ago

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

cozzyd11y ago

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

soylentcola11y ago

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

Did indeed crash Firefox 37.0.1.

malkia11y ago

Got a crash on Chrome (Linux)

mijoharas11y ago

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

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

1 more reply

Mizza11y ago

Hung, but eventually recovered on 37.

Not really sure what I was expecting.

skidoo11y ago

Well that's just mean.

j / k navigate · click thread line to collapse