Crashie.com lives again, locks up IE9

Many moons ago, actually August 31 2006, a website called crashie.com was launched. The purpose of the website was to, as you can guess by its name, crash IE. The idea was simple, a single line of code would cause most versions of IE7 and earlier to crash which forced you to use an alternative browser to view the sites content.

Many would think that the story ends there and the novelty site would fade into oblivion, unfortunately for Microsoft, that is not the case. Microsoft patched the flaw used for crashie.com in IE 8, which many thought would be the end of the website, but if you now visit crashie.com in IE9, the website locks up IE9 too.

What is actually causing the lockup of IE9 at this point is unknown, but Neowin was able to confirm on three different machines that the RTM of IE9 will lockup when visiting the website. While not good for Microsoft, those looking to play a joke on their IE9 using friends will have a new weapon for their tomfoolery.

Thanks for the tip wolftail

[Update] We are getting a mixed bag of reports, some say it loads without issue, others report that it locks up their system and one user reports a timeout.

Report a problem with article
Previous Story

Apple World Wide Developers Conference on June 6

Next Story

Warren Buffet warns against investing in social networks

118 Comments

Commenting is disabled on this article.

<script>for(x in document.write){document.write(x);}</script><input type crash>
This is not the web site's script (webmaster's) fault for the IE crashes, it is the Microsoft IE script engine's fault for not properly handling *simple* java scripts. ;-)
And this is valid for all IE editions/builds going way back to 4.0 [not tested earlier ones], and all the way up to 9.0 RTM.
A 64-bit OS + partial 64-bit IE browser engine do not/cannot protect against nor handle properly such faults/flaws.
Solution:
Stop bashing the website or your whining, and be constructive: start a petition/letter/similar to Microsoft to updated their script engine.
Because...
The script engine designed by MS needs to be redesigned, improved, updated, fixed, or whatever you prefer.

No decent web browser should be brought down by a single line of javascript code.
And guess what... no other browser suffers from this flaw. ;-)

Also, please understand that simple scripts like this 1 do not qualify as malware.
This script was posted only to demonstrate a design flaw in a browser engine, nothing else, and does just that, does not crash the OS, does not steal your personal info, does not install a virus/bot/trojan/rootkit/etc, does not redirect to a malware/spam web server.

HTH [Hope This Helps]

Ok, just was having a couple of techs test this site...

IE9 prompted the user that a script had been running too long, and asked to stop it. Clicking on stop halted the script and threw the proper error so that the scripting error could be reported if the user is participating in the customer experience improvement.

Wow, IE9 did exactly what it was suppose to do... Let's run out in the streets and call Microsoft stupid and evil!

Geesh

Seriously, this is news?

There is specific tricks that can lock EVERY browser.

There are ways to do recursive jscript or CSS or slam large chunks of data in unexpected places, and depending on the trick, report back as being active so that the crash prevention doesn't kick in.

This has nothing to do with IE. PERIOD.

Seriously look through the W3C standards and look at just the general ways to mess up a browser. Or flip through a few searches on browser specific ways to have any browser fail.

It didn't load. What's the point? These jerkoffs should do something more productive with their time, like jerking off (speaking of load).

Benjy91 said,
Stupid, I bet you could make a site that did this to any browser.

This site already does this for any browser (which disguises itself as IE).

sigh... AVG Free 2011 blocked some sorta javascript code thing that was meant to crash a computer... X( I will never ever ever figure out the AVG interface... so much for testing it out?

What is actually causing the lockup of IE9 at this point is unknown

So dumb, Neowin.. Even 10 years old would figure it out. Just remove this shameful "article" already.

Yes, this is why, they give IE: "<script>for(x in document.write){document.write(x);}for(;;)setInterval("void(0)",0)</script>" while everything else gets "<script>for(x in document.write){document.write(x);}</script>" ... You can see this below:

[root@main ~ ]# curl -A 'wget' http://www.crashie.com <script>for(x in document.write){document.write(x);}</script><input type crash>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DT...1-transitional.dtd">;
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
<head>
<title>Crash IE - Crash Internet Explorer</title>
##

[root@main ~ ]# curl -A 'Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)' http://www.crashie.com
<script>for(x in document.write){document.write(x);}for(;;)setInterval("void(0)",0)</script><input type crash>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DT...1-transitional.dtd">;
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
<head>
<title>Crash IE - Crash Internet Explorer</title>

thenonhacker said,
Because of this, I reported crashie.com as Web Forgery.
Is that a false report? Microsoft and Amazon send different webpages based on the browser user agent. Should you report them too?

Safari 5.0.4 on OS X 10.6.7 - changed UA to IE 7.0 - Whole browser crashes

Safari 5.0.4 on OS X 10.6.7 - changed UA to IE 6.0 - Whole browser crashes

Safari 5.0.4 on OS X 10.6.7 - changed UA to IE 8.0 - Browser goes REALLY slow for a while then works

I've change all the browser's user agent to that of IE and here's the result.

Internet Explorer 9: stuck in infinity loading loop
Firefox 4: whole browser crash
Chrome 11: crash with a sad tab
Opera 11: stuck in infinity loading loop
Safari 5: whole browser crash

day2die said,
I've change all the browser's user agent to that of IE and here's the result.

Internet Explorer 9: stuck in infinity loading loop
Firefox 4: whole browser crash
Chrome 11: crash with a sad tab
Opera 11: stuck in infinity loading loop
Safari 5: whole browser crash

On Safari running in OSX, I get the twirling ball and Safari is completely unresponsive. The menu bar doesn't even show up. Eventually, I get a dialog about the slow script asking if I want to stop running the script or continue.

On IE9 running in Windows Server 2008, the script locks up the tab, but IE is still responsive. I can open up a new tab, and continue to view other sites. Eventually, a notification pops up about the long-running script.

It seems to me, IE9 handles the situation the most elegantly even though the site is designed with the intention of making IE look bad.

bj55555 said,

On IE9 running in Windows Server 2008, the script locks up the tab, but IE is still responsive. I can open up a new tab, and continue to view other sites. Eventually, a notification pops up about the long-running script.

Internet Explorer separate each tab into its own process: that's probably why.

Move along, folks. Nothing to see here. The website does nothing but load some stupid infinite loop script if IE is detected in your user agent string. The site isn't exploiting some flaw in IE. The same script will lock up any browser. It's already been proven that IE won't crash/lock up if you change the user agent to anything other than IE, and it's already been proven that other browsers will crash/lock up if you change the user agent string to IE. The site is clearly run by some douchebag(s).

Site works/loads perfectly fine in my Opera 11.01. No errors, no nothing.

About to test with IE 9.
It took it about 5 minutes of just setting there to lock IE up. Normally wouldn't set at any site that long waiting for anything to happen though.

Just tested site with Seamonkey 2.0.13 and it works perfectly fine also.

cork1958 said,
Site works/loads perfectly fine in my Opera 11.01. No errors, no nothing.

About to test with IE 9.
It took it about 5 minutes of just setting there to lock IE up. Normally wouldn't set at any site that long waiting for anything to happen though.

Just tested site with Seamonkey 2.0.13 and it works perfectly fine also.


You need to change the user agent of those browsers to that of IE for the infinity loop to load.

Edited by illegaloperation, Mar 28 2011, 6:10pm :

Brad Sams,
I want you to add to the article that the site is targeting Internet Explorer's user agent and both Firefox and Chrome with Internet Explorer's user agent will crash.

day2die said,
Brad Sams,
I want you to add to the article that the site is targeting Internet Explorer's user agent and both Firefox and Chrome with Internet Explorer's user agent will crash.

+1

http://www.crashie.com has lost its credibility. It qualifies as malware.

Hi. I wish to report that my IE9 RTW IS NOT CRASHING AT ALL.

IE9 shows a msg at bottom that "crashie.com is not responding" with a "Recover Webpage" button in the msg box. I am running crashie.com in a tab as I type this comment. The whole of IE9 is behaving as completely normal and is responsive.

Even in the tab running crashie.com, the 'circular' aero-like 'loading' button is also 'rotating' without hiccups, so it means IE9 is not hanging or crashing at all.

What I did was, after installing IE9 RTW (on top of RC), I uninstalled IE8 from my machine since I will never use it again. Removing IE8 removed 10 more updates, but my system remains absolutely up-to-date. I am running Windows Vista Home Premium (32-bit) with SP2, the Platform Update and Platform Update Supplement for Vista.
CAN ANYONE CONFIRM THIS?

in4 said,
Hi. I wish to report that my IE9 RTW IS NOT CRASHING AT ALL.

IE9 shows a msg at bottom that "crashie.com is not responding" with a "Recover Webpage" button in the msg box. I am running crashie.com in a tab as I type this comment. The whole of IE9 is behaving as completely normal and is responsive.

Even in the tab running crashie.com, the 'circular' aero-like 'loading' button is also 'rotating' without hiccups, so it means IE9 is not hanging or crashing at all.

What I did was, after installing IE9 RTW (on top of RC), I uninstalled IE8 from my machine since I will never use it again. Removing IE8 removed 10 more updates, but my system remains absolutely up-to-date. I am running Windows Vista Home Premium (32-bit) with SP2, the Platform Update and Platform Update Supplement for Vista.
CAN ANYONE CONFIRM THIS?

IE9 is doing what it's supposed to. The tabs run in their own process, so when the script bogs the tab it's running in down the other sessions will still work.

Doesn't crash on mine either. Seriously, are you guys turning into Engadget? This is NOT news. I don't get why it's so cool to hate on IE, crash bugs are normal and happens with every software.

Go-Go Sheeps! Try it till it burn, then, burn it more!

Well, serious now, to Crash or not to Crash, I'm not willing to test it. MS, get the job done as fast as possible!

Doesn't crash my IE9 either.
CrashIE is just fooling around itself with an infinity script, while I happily open tabs, open menus, search on Bing, then Google, the beauty of the web.

Locks up IE9 here.. I get an unresponsive script error, try to hit stop script, IE grays out with a not-responding alert, I had to kill the process.

The test is entire BS.

I changed IE9's user agent to Firefox 4 and later to Chrome 10 and IE9 loaded the page correctly.

I've tried changing Firefox 4's user agent to IE9 and get an infinite loading loop.

I think you're right, they simply create an infinite loading loop. - hardly a fault of the browser when the web coder does that intentionally.
I can cause a web server to crash too if I make some infinite loops in my ASP/PHP ... BS site as you say.

day2die said,
The test is entire BS.

I changed IE9's user agent to Firefox 4 and later to Chrome 10 and IE9 loaded the page correctly.

I've tried changing Firefox 4's user agent to IE9 and get an infinite loading loop.

That's funny. It must be disabling the loop script if it's not IE.

No crash.... the tab is trying to load then it asks to end a long running scrpt and that's it. On the second tab I am vieweing neowin and typing this comment.

Didn't load, but it doesn't crash ie9, I could open other pages and have lots of tabs even with crashie open.

Did not crash my installation of Internet Explorer 9. Tried both the x86 and x64 flavor with this site on both Windows 7 x64. Now, it never crashes but the page never loads. However it DOES crash both the x86 and x64 version of Internet Explorer 9 on my install of Windows Server 2008 R2.

Fail website in my opinion trying to persuade people not to use IE9 just because of the browsers' past not being so.. friendly. I'm rather surprised this article was even allowed as its a rather pointless one that just is trying to give the website more attention in my opinion.

Honestly, I've seen both Chrome and Firefox have its fair share of crashes even the most recent release of Firefox seems to suck the RAM on both my computers dry while any other browser works relatively fine.

Mine didn't crash, it uses full cpu power of one of my cpu's cores though. It's been almost a minute and no notifications that the script is long, I just have a not responding browser now.

Didn't crash here with IE9 on Win7 64bit. Just got the notification bar informing me about long running script.

Zkal said,
Didn't crash here with IE9 on Win7 64bit. Just got the notification bar informing me about long running script.

Me too, on 32 bit PC.

Benjy91 said,
I want to try it But I dont have IE, and im not downloading it, restarting, just to test.

An IE9 install does not require a restart, unless you have the beta or RC.

daniel_rh said,
Yep, it crashes my IE9

Using Windows 7 64bits, final IE9, all updates applied

Me too completely crashed - Server 2008 R2 with IE9. Crashed other tabs too - not just the crashie one.

daniel_rh said,
Yep, it crashes my IE9

Using Windows 7 64bits, final IE9, all updates applied

Yep same here. Except the update that came out the last few seconds. You know micro soft and their perfect security that needs patching every second. Makes life interesting. Not that i am interested in that!?

It's just a script line that does infinite recursive document.writes. It didn't crash mine, it just bogged it down. All this does is drive more advertising hits to his site. (It's loaded with hidden ad scripts.)

I did something similar in the Windows Me days. I just created a page that had an infinite loop and the browser would stop responding.

Tom W said,
Are you serious? This doesn't crash Internet Explorer 9 at all.

it froze my PC when I ran it in IE9 - shows a nice little web page when looking at it via Chrome

Shaun. said,

it froze my PC when I ran it in IE9 - shows a nice little web page when looking at it via Chrome

Same here

No crash for me either. Site just will never load, but IE is responding.

Opera won't load it as well
"This page has been reported for distributing malicious software. Visiting this page may be harmful."

Yeah.. and I can crash the latest Google Chrome by pasting a majorly long text document in the Address Bar, try it yourself. This is all this website is doing is writing out a load of **** constantly..

SuperKid said,
Yeah.. and I can crash the latest Google Chrome by pasting a majorly long text document in the Address Bar, try it yourself. This is all this website is doing is writing out a load of **** constantly..

Change Chrome's user agent to this and it will crash:
Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)

day2die said,

Change Chrome's user agent to this and it will crash:
Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)

Agreed. Loaded fine in Opera.
Changed user agent to IE, page wouldn't load but browser became laggy. CPU nor RAM rose noticeably high. After a couple of minutes closed the tab and all was fine again.

It's a rather pathetic way attack IE users by targeting them in this manner =/

MarkusDarkus said,
Didn't crash my IE.

I got a message about the site not responding due to a long running script. IE9 als gave me a button to stop the script, which then caused the tab (not the whole browser) to crash. I was then able to just close the tab and continue using IE just fine.

I guess thats a +1 for the tab isolation technology in IE9. One site crashes, it doesn't take down the whole browser.!

MarkusDarkus said,
Didn't crash my IE.

Crashed mine immediately, works just fine in Chrome... which is generally the case, and why I use Chrome. IE sucks.

negroplasty said,

Crashed mine immediately, works just fine in Chrome... which is generally the case, and why I use Chrome. IE sucks.


The site target IE's user agent. Also, with both Internet Explorer and Chrome using IE's user agent, Chrome crash, but Internet Explorer doesn't.

You should reconsider your "IE sucks" statement and replaced it with "Chrome sucks".

day2die said,

The site target IE's user agent. Also, with both Internet Explorer and Chrome using IE's user agent, Chrome crash, but Internet Explorer doesn't.

You should reconsider your "IE sucks" statement and replaced it with "Chrome sucks".

Regardless of it targeting the IE useragent... IE does suck in comparison to Chrome and there isn't a single real world test/benchmark that will show otherwise. IE sucks, and it has a long way to go until it doesn't... I do acknowledge IE9 is a big step in the right direction for Microsoft, but it just doesn't stand up to the competition. Oh, and while I'm at it... Firefox also sucks.

negroplasty said,

Regardless of it targeting the IE useragent... IE does suck in comparison to Chrome and there isn't a single real world test/benchmark that will show otherwise. IE sucks, and it has a long way to go until it doesn't... I do acknowledge IE9 is a big step in the right direction for Microsoft, but it just doesn't stand up to the competition. Oh, and while I'm at it... Firefox also sucks.


IE9 sucks so bad it didn't crash, but Chrome 11 did.

negroplasty said,

Crashed mine immediately, works just fine in Chrome... which is generally the case, and why I use Chrome. IE sucks.


- Even on Chrome (latest Dev build) it crashed.. Not only IE9..!