Slashdot Mirror


HTML Rendering Crashes IE

SlimySlimy writes "According to this article on Secunia, a new IE exploit was found that crashes almost any version of Internet Explorer past 4.0 with just 5 lines of plain HTML code (no JavaScript, ActiveX, etc.). If you're very brave, you can test/crash your IE by going here." There's also a note on SecurityFocus.

887 comments

  1. Inquirer says one line by A+nonymous+Coward · · Score: 4, Informative
    1. Re:Inquirer says one line by jtilak · · Score: 1

      um its html so technically the whole 234234213 tags could be on one line.

    2. Re:Inquirer says one line by Anonymous Coward · · Score: 0
      No. Think like Larry Wall:

      <html><form><input type crash></form></html>

    3. Re:Inquirer says one line by Selanit · · Score: 4, Insightful

      I just crashed my copy of IE (5.00.2614.3500) with no more than .

      And anyway, even if your version requires more than that, it can still be all on one line, eg:

      <html><form><input type crash></form></html>

      Since carriage return/line feed pairs are totally unimportant in HTML (except with the <pre> tag, and maybe one or two others), it's silly to talk about how many "lines" it takes anyway.

    4. Re:Inquirer says one line by Anonymous Coward · · Score: 0
      actually, just the line
      <input type>
      is enough to crash my IE (IE6 under XP SP1)
    5. Re:Inquirer says one line by lseltzer · · Score: 1

      Same here. The word "crash" is obviously irrelevant. Just '' doesn't crash it though.

    6. Re:Inquirer says one line by Jugalator · · Score: 1

      The shortest line should be:

      <input type>

      --
      Beware: In C++, your friends can see your privates!
    7. Re:Inquirer says one line by craigeyb · · Score: 3, Interesting

      Not to be overly trollish here, but you could also squish poetry onto one long line or a big novel onto one really huge page, like something in Guinness's Book of World Records I suppose.

      The point is, we use line counts in computer languages, even though most computer languages can be spaced out in numerous ways, because it provides a good rough estimate of length and complexity. It's not always the best metric, but oftentimes it serves its purpose well. In this case, the typical slashdot reader can see that the exploit is only "five lines" and realize that it's not a overly complicated HTML parser exploit but instead something ridiculously simple.

      --

      Social Contract? I don't remember signing any Social Contract!

    8. Re:Inquirer says one line by norweigiantroll · · Score: 5, Funny

      <input type crash>
      It's not a bug, it's a feature! The "crash" input type allows the user to crash the browser. It's very useful and another Microsoft (TM) innovation.

    9. Re:Inquirer says one line by cryptor3 · · Score: 1

      Quote:
      Since carriage return/line feed pairs are totally unimportant in HTML (except with the <pre> tag, and maybe one or two others), it's silly to talk about how many "lines" it takes anyway.

      <html><form><input type crash></form></html></tt>

      OK, fine. Then it's 44 bytes. IE6 (and maybe others) can be crashed with 38 bytes.

      <tt><html><form><input type></form></html></tt>

      And actually, if you're talking about bugs, maybe the bug requires you to have it on 5 lines. This one doesn't, but there might be some bug that does.

    10. Re:Inquirer says one line by iabervon · · Score: 1

      A lot of pages already contain a form tag, though, so it is sufficient to add one line to an existing document. You can crash IE with a 5 line document, or with one line in a document.

    11. Re:Inquirer says one line by ersgameboy · · Score: 1

      I just made a new HTML file, with just the one line (no HTML tags, even), and it crashed my IE install the same way the initial link did. (I'm running IE 6.0, build 2600, 128-bit encryption on a PII-450 with 98SE)

    12. Re:Inquirer says one line by Anonymous Coward · · Score: 0

      LOL. I just made an HTML document that says:

      I loaded it, and it crashes instantly. LOL. stupid M$...

    13. Re:Inquirer says one line by Anonymous Coward · · Score: 0

      mine will crash with just

    14. Re:Inquirer says one line by revscat · · Score: 1

      Since carriage return/line feed pairs are totally unimportant in HTML...

      Should be, but aren't in IE. I don't have the code here at home, but we have had bugs in IE before where the fix was to put the table cell tags on a single line. It's nothing major, but there were 1-pixel differences that QA bounced back to us and which took forever to figure out. And the only difference between the working code and the broken code was the presence of new lines.

    15. Re:Inquirer says one line by Anonymous Coward · · Score: 1, Insightful

      ok got bored, fired up this 98 box, and entered into the location on "my 'puter"
      insta-crash of the windows explorer thingie, but good old netscpe still kicks.

      You guy's are slacking! You should have found this sooner, think of all the fun we missed! It is bad enough that Microsoft has little to no QC, now the Slashdot community is sitting on their collective haunches, not sending malformed code to IE.
      We are running out of exploits people! What are we going to do for fun when Microsoft patches all these known holes? Well, what then?
      Do you think all a company like Microsoft has to do is innovate these new ammusements for us? Billy-G is going to start charging us for this, an entertainment tax, possibly. Come on, it costs Billions and Billions of Bucks to make software this good, just think how buggy and unstable software would be if you didn't pay for it....

      Oh, wait

      I never bought Linux
      or FreeBSD
      or my Freesco router software...

      and this win98 came "free" with the computer, so it must be just as good, right?

  2. Wonder if that works deeper in a page by ShieldW0lf · · Score: 4, Funny

    Could wreak havoc in html-enabled forums

    --
    -1 Uncomfortable Truth
    1. Re:Wonder if that works deeper in a page by Anonymous Coward · · Score: 0

      Probably some havok, but most forums only allow a few select tags.

    2. Re:Wonder if that works deeper in a page by zook · · Score: 5, Informative

      I doubt it. From my quick toying around, it seems that if the offending tag appears inside of a tag there's no such effect.

      It's hard to divine the exact fatal combination, of course. :)

    3. Re:Wonder if that works deeper in a page by Whalephant · · Score: 0

      Some time ago I found out how to reboot or shut down windows 2000 systems by going to one particular web page. I really don't know what causes this but I tested it with three different win2k systems and it "worked" just fine... win xp didn't have this feature.

      Try it by going to url www.nst-lappeenranta.net (homepage of finnish salibandy team)
      On left side of the page choose link "Naiset edustus", then on the same side of the page link "Galleria", and then in the middle of the page link "Vilkaisu menneeseen" and boot...

      at this moment I am not able to test if the "feature" is still there.

    4. Re:Wonder if that works deeper in a page by Guanix · · Score: 1

      You can use an . (Presumably that's allowed in any HTML-enabled forum that allows .)

    5. Re:Wonder if that works deeper in a page by goph · · Score: 3, Interesting

      actually it could indeed...

      just putting "about:<input type crash>" in the url bar already worked...

      which is just 1 line

    6. Re:Wonder if that works deeper in a page by Guanix · · Score: 1

      I meant, you can use an IFRAME tag. That's presumably allowed in any HTML-enabled forum that allows INPUT. (Why are the less-than and greater-than symbols censored in Plain Old Text?)

    7. Re:Wonder if that works deeper in a page by UserGoogol · · Score: 1

      Because Plain Old Text mode is phenomenally stupid for some reason. You want Extrans (html tags to text) mode.

      --
      "Never attribute to malice that which can be adequately explained by stupidity." -- Hanlon's Razor
    8. Re:Wonder if that works deeper in a page by mr3038 · · Score: 2, Informative
      Make it shorter. Just type
      about:<input type>
      in the url bar and IE crashes.

      The important thing is to leave the value of type attribute undefined.

      For example, this works too:
      about:<input with sans-serif type "ALL YOUR BASE ARE BELONG TO US">

      --
      _________________________
      Spelling and grammar mistakes left as an exercise for the reader.
    9. Re: Wonder if that works deeper in a page by Black+Parrot · · Score: 1


      Might be a useful way of chasing off dorks who post HTML to Usenet.

      --
      Sheesh, evil *and* a jerk. -- Jade
    10. Re:Wonder if that works deeper in a page by dattaway · · Score: 2, Interesting

      Does this work as a ">link?

      If it does, I can imagine many people posting malicious links in blogs everywhere by the end of the day.

    11. Re:Wonder if that works deeper in a page by blibbleblobble · · Score: 1

      "just putting "about:" in the url bar already worked..."

      Yep. This has been floating around bugtraq for weeks, so if you missed it:

      <input type crash>

      That, in any web-page, will cure you of your IE-using website visitors.

    12. Re:Wonder if that works deeper in a page by fbg111 · · Score: 1

      It also appears that if you declare the document as XML, it doesn't crash IE either.

      --
      Flying is easy, just throw yourself at the ground and miss. -Douglas Adams
    13. Re:Wonder if that works deeper in a page by Anonymous Coward · · Score: 0

      You mean this will kill IE?

    14. Re:Wonder if that works deeper in a page by Anonymous Coward · · Score: 3, Informative

      BTW, the above link does not make use of the about-link method to inject the malicious code. Slashcode filters attempts to use about: in links and IE does not follow redirects to the about: protocol. Also the most well known URL obfuscating redirector, http://yahoo.com?http://host/foo/bar.html, won't redirect to about: anyway. The script which is addressed by the above URL does not filter the URL data which it then uses in the redirection announcement. It's not my script or webserver, and if I had taken proper precautions, that link would not be traceable to me. It is also possible to further obfuscate the target by chaining it with the yahoo redirector: bye bye. With this method, anyone who knows the URL of an amateurish script like the one mentioned above, can post "killer-links" to message boards.

    15. Re:Wonder if that works deeper in a page by Anonymous Coward · · Score: 0

      Yes, it does, but Slashcode filters certain combinations of protocols and escape characters in links. This comment explains how to use a litte external help to get around some link safety filters.

    16. Re:Wonder if that works deeper in a page by gazbo · · Score: 1

      Well, I just get a picture - then again, I actually know how to keep a system patched so I'm not running 3 year old bugs.

    17. Re:Wonder if that works deeper in a page by minion · · Score: 1

      Heh, now everyone running one of those stupid Windows CE Phones could get a text message that rebooted their phone.

      --

      -- If we don't stand up for our rights, now, there will be no right to stand up for them later.
    18. Re:Wonder if that works deeper in a page by RzUpAnmsCwrds · · Score: 2, Informative

      As of IE6SP1, the about: protocol is disabled, and this no longer works (you can still get it, of course, by going to a page).

    19. Re:Wonder if that works deeper in a page by Anonymous Coward · · Score: 0

      When you right-click, "Save Target As...", and then using the file browser and just right click on it to hopefully edit it with notepad, it tanks well before the options are completely rendered. (I am using 2k)

      Again, not even accessing it via IE, it dies.

      I tried to view the source code, but I had to go start->run->cmd->edit new.htm

    20. Re:Wonder if that works deeper in a page by Wingnut64 · · Score: 1

      On that subject, there's a link here you might be interested in.

      --
      echo 'Header append X-HD-DVD "0x09f911029d74e35bd84156c5635688c0"' >> /etc/apache2/httpd.conf
    21. Re:Wonder if that works deeper in a page by Anonymous Coward · · Score: 0

      > I tried to view the source code, but I had to go start->run->cmd->edit new.htm

      Why not just rename it to new.txt?

  3. OS X IE Is Unaffected by WiseWeasel · · Score: 5, Interesting

    It seems that IE 5.x on MacOS X is not affected by this. Not that it's such a big deal, I imagine any affected Windows versions of IE can be relaunched and people will just avoid going to places with such code. I fail to see the significance. Oh well, glad to see their Mac port is more stable in this regard.

    --
    "I like systems, their application excepted", George Sand (French)
    1. Re:OS X IE Is Unaffected by slamb · · Score: 1
      Not that it's such a big deal, I imagine any affected Windows versions of IE can be relaunched and people will just avoid going to places with such code. I fail to see the significance.

      If this is just a denial of service attack, you're probably right. But it's often the case that when you can crash software, you can insert arbitrary code. (Buffer overflows, format string vulnerabilities...the most common causes of segfaults.) So what makes this really worrisome is not the inconvenience of restarting the browser but the fear that any website you go to can completely compromise your machine.

    2. Re:OS X IE Is Unaffected by Chroneos · · Score: 1, Informative

      Do you ever notice that when Microsoft makes a Mac version of a piss-poor Windows product that it tends to not suck [as much]?

      Of course I'm not saying that I use Mac IE, but if it came down to using IE and gnawing my own leg off, I'd still have two legs at a Mac. ;-)

      --
      ------------ Ben Chroneos
    3. Re:OS X IE Is Unaffected by petecarlson · · Score: 2, Funny

      When I clicked the crash link,Explorer crashed but then relaunched all by itself. First time I have ever seen that happen.
      Running IE 6 on 2000 pro.
      guess I have to fire up Mo*illa to see what the lines of html are.

      # There is a key broken on my laptop and I am not
      # getting out of bed at four in the morning to
      # plug in the keyboard

    4. Re:OS X IE Is Unaffected by Elwood+P+Dowd · · Score: 4, Insightful

      Somehow I imagine that the folks at securityfocus.com would check pretty carefully for that. If there were serious danger involved, they'd either give MS some time to fix it before this release, or they would have told us the whole story.

      So hold your chickens before they jump the conclusion.

      --

      There are no trails. There are no trees out here.
    5. Re:OS X IE Is Unaffected by Anonymous Coward · · Score: 5, Funny

      It seems that IE 5.x on MacOS X is not affected by this.

      I've had it. I'm switching.

    6. Re:OS X IE Is Unaffected by Anonymous Coward · · Score: 1, Funny

      it was all like "beep beep beep" and then my browser crashed! and it was a really good website!

    7. Re:OS X IE Is Unaffected by Zan+Zu+from+Eridu · · Score: 2, Interesting

      Seems to me like the people at securityfocus missed something: what would happen if someone where to put up a page that changes IEs default startup url to about:<input type about> or something like that?

    8. Re:OS X IE Is Unaffected by Anonymous Coward · · Score: 0

      OMG that's the funniest thing I've read in a while (from the Ellen Feiss Switch ad btw)

    9. Re:OS X IE Is Unaffected by exhilaration · · Score: 1

      oooooooooooooooooh - INTERESTING IDEA, but wouldn't you have to either 1) point to an existing web page with the malicious code or 2) create a local file with the malicious code and make that the home page? Is it possible to create the malicious code on the fly with javascript without accessing any outside resource? Can someone come up with a URL that exploits this bug?

    10. Re:OS X IE Is Unaffected by AsylumWraith · · Score: 1

      Simple, right click on the IE icon, and choose Properties. Change the homepage setting from there.

      This works in IE 6, I don't know if it's valid for earlier versions.

    11. Re:OS X IE Is Unaffected by schon · · Score: 1

      Simple, right click on the IE icon, and choose Properties. Change the homepage setting from there.

      But how many IE users would know to do that?

      Probably only a tiny fraction of the number that even know you can change the homepage at all - which (from my experience) isn't a whole lot.

    12. Re:OS X IE Is Unaffected by Anonymous Coward · · Score: 0

      I wonder if this is because the rendering engine on OS X is the old generation rendering engine vs. the new engine they use on Windows (codename trident.)

    13. Re:OS X IE Is Unaffected by Anonymous Coward · · Score: 0

      I've had it. I'm switching.

      Some of us do not have the money to switch.
      For some of us poor working class droogs all we can do is install slackware/debian/*BSD and start kickin ass with a techno cl@ss w@r against the rich yuppie scum who inhabit the lands of microsoft and apple!

      Up against the wall Bill Gates! Up against the wall all you TiBook carrying, VW drivin, birkinstockwearin yuppie scum! Feel my steal toe capped oxblood DM as it kicks in your soft yuppie skull! All power to the class war!

    14. Re:OS X IE Is Unaffected by neuroticia · · Score: 1

      Currently, probably not many. But if there were to be a malicious little snippet of code that changed their homepage to the crash page, and it did this to a lot of people, the knowledge would spread pretty quickly. Especially since most non-geeks have geek friends that they can email/IM and yammer at until they find a solution. Then there will be the little news snippets on TV... And the magazines that love to have every over-used troubleshooting technique.

      I don't see the "lack of knowledge" in this area being a major one. If someone uses IE on a regular basis and suddenly can't use IE, they'll figure out how to use it again. This is a very different situation than all those nasty little root exploits that don't give the end-user any visible grief at all, and thus don't warrant any attempt to fix. ;)

      Anything that effects a user's applications in an *obvious* way worries them, even if it's not dangerous at all. Whereas, truly dangerous things that don't impact the end-user's perception of their machine--doesn't seem to bother them. Look at all the nice little virus-infected windows computers that are out there trying to spread their viruses--and no one seems to give a damn because the machines appear to continue functioning for the "important" stuff like surfing the web and checking email.

      -Sara

    15. Re:OS X IE Is Unaffected by Smurf · · Score: 1
      I wonder if this is because the rendering engine on OS X is the old generation rendering engine vs. the new engine they use on Windows (codename trident.)
      It also crashes IE 4 on Windows, and I believe it also uses an old generation rendering engine.
    16. Re:OS X IE Is Unaffected by RevAaron · · Score: 1

      Nope, the rendering in engine is completely different from anything in Windows or Unix IE. It was written from the ground up seperately, it's not merely a port. I imagine there is some code shared between the two versions, but perhaps not even much of that.

      --

      Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
    17. Re:OS X IE Is Unaffected by mosch · · Score: 1

      the rendering engine used by IE/Mac is completely different from the one used in IE/Windows. This is why IE5/Mac had so much better support for CSS and such than IE5/Win.

    18. Re:OS X IE Is Unaffected by bhtooefr · · Score: 0

      In a previous article on Xupiter, they were talking about users blindly clicking "Yes" in popup dialogs, and stuff installing on their computers. It is very easy (a very small snippet of JavaScript will do the job) to make a "Would you like to make 'about:' your homepage?" box. Google is one example (click "Make Google Your Homepage!"). Many sites will throw these on you without asking.

    19. Re:OS X IE Is Unaffected by PetWolverine · · Score: 1

      Hey, Doc--I gotta buy you like a proverb book or somethin. This mix 'n match shit's gotta go.
      --The Funny Man, Boondock Saints

      --
      I found the meaning of life the other day, but I had write-only access.
    20. Re:OS X IE Is Unaffected by schon · · Score: 1

      I don't see the "lack of knowledge" in this area being a major one.

      I think you've never had to deal with an average user.

      Most people don't know that they can change their homepage, because they don't want to know. When the computer crashes, or locks up, they get someone to fix it for them. And the next time it happens, they get that someone to fix it again.

      Note I'm not saying this is a bad thing - when I have to fix someone's computer, I don't berate them for not knowing something.. they shouldn't have to know most of the stuff that geeks think everybody should know..

      Lots of people don't change the oil in their car - they get a mechanic to do it (this includes me, BTW, although not because I don't know how.)

      If someone uses IE on a regular basis and suddenly can't use IE, they'll figure out how to use it again.

      Again, I have to conclude by this that you don't know any average users.

      The average user will try a few times, then simply not use it any more, until they can get someone to fix it for them. This person might tell them how to fix it, but the user will forget, because they don't do it often enough to remember.

    21. Re:OS X IE Is Unaffected by cide1 · · Score: 1

      I have to second that, it made me crack a smile.

      --
      -- the computer doesn't want any beer, no matter how much you think it does. NEVER, EVER feed your computer beer.
    22. Re:OS X IE Is Unaffected by neuroticia · · Score: 1

      I think you've never had to deal with explaining a complex topic to a sub-average user, because explaining to an "average" user how to change a homepage is a piece of cake, whereas explaining to my sister how to open a .jpg file off a CD, re-size it so that it's not ridiculously large, attach it to an email, and send it to me is NOT a piece of cake. *THAT* is a pain in the ass. Explaining how to change a homepage, by comparison, is pitifully simple.

      As for "They'll figure out how to use it again"--this means either doing the 10 minutes of research that average-bright users do, or instant messaging their personal ubergeek and saying "HELP!", now the ubergeek is more than likely to know of the problem. Besides, it's pretty much as simple as creating a fixhomepage.reg file with

      [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main]
      "Start Page"="http://www.google.com"

      and having the user download it, and double click it. Presto-changeo, the homepage is now google.com

      So, basically the average user just has to be able to say "Err. This isn't working" and contact that uber-geek that *every* average user has, and the ubergeek will either give them a registry key similar to the one above, or step them through fixing it.

      I never claimed "When necessary, all average users will grow brains". I know that's impossible. ;)

      -Sara

    23. Re:OS X IE Is Unaffected by Anonymous Coward · · Score: 0

      That mus have been like . . .

      a bummer.

  4. mozilla crashes too by Anonymous Coward · · Score: 5, Informative

    I use galeon most of the time and it crashes often too... Just put this in a document

    <body onblur="javascript:self.focus()">

    browse it, and galeon will crash (as of 1.3.3.20030419). Do the same in mozilla, close the browser window, and it will segfault (version 1.3).

    1. Re:mozilla crashes too by magnum3065 · · Score: 0, Redundant

      Hmm, no problem on Phoenix build 20030407. Tried it turning on and off the ability for JavaScript to raise and lower windows.

    2. Re:mozilla crashes too by Hein_or_Henk · · Score: 1

      No problem with Mozilla 1.3 either.....

      --
      -- This message was made with 100% recycled electrons.
    3. Re:mozilla crashes too by arvindn · · Score: 5, Interesting
      Even simpler:

      <script> for(;;){window.open('');} </script>

      Just tried with mozilla 1.2.1: froze.

      OTOH:

      <script> for(;;){} </script>

      If I do this a dialog pops up saying: "A script on this page is trying to screw you. Do you want to kill it?" (not in those words though :)

    4. Re:mozilla crashes too by metalpet · · Score: 5, Interesting

      That's actuallly a good point.
      Everybody who has spent any time developing web pages has learnt that bad (and sometimes even good) html can crash browsers.

      Are we *that* confident in the maturity of our web browsers that causing a browser crash is nowadays considered a serious issue?

      Before jumping the gun on parsing errors that kill the app, it might be smart to go over design errors first (scripts that keeps on going and that bypass the simple "lengthy script" checks are a good example. recursive frameset tricks would qualify too.). I've yet to see a full-featured browser that doesn't choke and/or die when presented with the right mix of recursion, active content and wickedness.

      <tidbit type=outdated>
      Netscape 3 had a neat crash code:
      <script>delete new Location</script>
      The neat part about it is that 2 of those 3 words were undocumented.
      Of course any attempt to pass that as a security concern back then would have been laughed at. loudly.
      I'm not sure what has fundamentally changed since then.
      </tidbit>

    5. Re:mozilla crashes too by JimDabell · · Score: 4, Insightful

      Everybody who has spent any time developing web pages has learnt that bad (and sometimes even good) html can crash browsers.

      I can't think of a browser released in the past couple of years that *crashes* on bad HTML, except for this particular issue. Misrenders, yes, but crashes, no. Bad javascript is another issue; you can protect yourself from that quite easily, and most of the time the browser catches infinite loops, fork bomb-style attacks, etc anyway.

      <tidbit type=outdated>
      Netscape 3 had a neat crash code:
      <script>delete new Location</script> The neat part about it is that 2 of those 3 words were undocumented.
      Of course any attempt to pass that as a security concern back then would have been laughed at. loudly.
      I'm not sure what has fundamentally changed since then.
      </tidbit>

      IE has become a standard part of the Windows OS. As more and more applications use it, the impact of crashing greatly increases.

    6. Re:mozilla crashes too by Anonymous Coward · · Score: 0

      The following code immediately crashes most Netscape 4.x browsers (on all platforms). Only in the late 4.7x releases has this bug been fixed.

      <table><tr><td style="padding: 5">
      <blockquote>some text</blockquote>
      <table><tr><td>some text</td></tr></table>
      </td></tr></table>

    7. Re:mozilla crashes too by Anonymous Coward · · Score: 0

      i'm just supporting the poster above and flaming the responders ;)

      blah blah blah - its obvious who are Not programmers in a small team/group world.

      surely a bit of programming is about making things work - and not simply by complaining about the code on a +-level from where you are. yes - i've bithched about code that i am integrating - but i either fix it or work around it. not ideal i know but more real world i'm afraid.

      tell me - you guys are either working a Huge company where you can hide safely away* - or you are managment?

      *correction... i suppose... larger companies can cater for these glitches by getting them corrected but the smaller teams on tighter budgets have to simply make do.
      extreme eg. humble me complains about bug like this to MS. is it corrected ... hmmm... unlikely really, so the soultion? - use different code.

      oh yeah, (i believe) not everyone with knowledge of these issues is going to use them are they.(?)

    8. Re:mozilla crashes too by JimDabell · · Score: 1

      That Netscape major version is over five years old. I am well aware of the problems with Netscape 4.x and CSS, not to mention a hell of a lot of other problems with that browser. If you use Netscape 4.x as a measuring stick for the statement:

      Are we *that* confident in the maturity of our web browsers that causing a browser crash is nowadays considered a serious issue?

      ...then I think the answer is "I'm not confident that "our web browsers" won't burn down my house and steal my gran's pension. Netscape 4.x is evil. I trust IE more than I trust Netscape 4.x.

    9. Re:mozilla crashes too by rmdyer · · Score: 1

      umm, would you like to expand on "you can protect yourself from that (javascript) quite easily"? Just -how- do you protect yourself? eh? Just what browser allows you to specify what javascript commands can run and which can't?

      BTW, i'd love to see a browser like that. I'd like to see a browser with a reverse style cookie management too. One where you can selectively deny cookie lookups instead of cookie stores.

      +2 cents.

    10. Re:mozilla crashes too by craigeyb · · Score: 4, Funny

      ...and most of the time the browser catches infinite loops...

      Give it up for the Halting Problem Solution. Whoo whoo!

      --

      Social Contract? I don't remember signing any Social Contract!

    11. Re:mozilla crashes too by Trailer+Trash · · Score: 1

      Everybody who has spent any time developing web pages has learnt that bad (and sometimes even good) html can crash browsers.

      The funny thing is, though, "<input type crash>" isn't HTML. It looks kind of like HTML, but it *isn't*.

      It's moronic that a simple text sequence can crash the browser, but if the title is going to be "HTML Rendering Crashes IE", then show me some actual HTML that will crash IE.

      Michael

    12. Re:mozilla crashes too by Ktulu_03 · · Score: 0

      My version of Konqueror (KDE 3.1) doesn't crash when I go to that page though... -Kevin

    13. Re:mozilla crashes too by JimDabell · · Score: 1

      Since when does any script on a normal website need to run more than a few seconds without halting? You don't need to solve the Halting Problem to catch problems with javascript.

    14. Re:mozilla crashes too by JimDabell · · Score: 1

      umm, would you like to expand on "you can protect yourself from that (javascript) quite easily"?

      Switch off javascript, or if there are some sites you want to keep it on for, allow it for certain domains. You can do this in Mozilla, Konqueror, and even IE, usually.

    15. Re:mozilla crashes too by Anonymous Coward · · Score: 0

      I can't think of a browser released in the past couple of years that *crashes* on bad HTML, except for this particular issue. Misrenders, yes, but crashes, no.

      Bad HTML has been known to crash or freeze browsers for a long time. To me a freeze is just as bad as a crash because it leaves your browser unusable. A great example of this is Cyberarmys old crash page, which was designed to crash any browser. When i went today i noticed it was gone, I dont know how long ago they took it down, but I found a copy on google here (WARNING - It may crash of freeze your browser - it froze my Mozilla 1.3).

      I think the problems existed, but they werent as publicized because a crash and an exploit that gave an attacker control of your machine are very different. A crash is just inconvienent, but getting owned sucks.

    16. Re:mozilla crashes too by Anonymous Coward · · Score: 0

      didn't do nothin to dillo

    17. Re:mozilla crashes too by Wastl · · Score: 2, Interesting
      Since when does any script on a normal website need to run more than a few seconds without halting?

      Can you guarantee that? I had a student who was using JavaScript in an editor written in dynamic HTML to traverse the HTML DOM tree in Mozilla and reconstruct information out of it to form an XML document. The program takes several seconds even on relatively small documents. Where would you put a reasonable timeout?

      Sebastian

    18. Re:mozilla crashes too by powerlinekid · · Score: 1

      The for(;;){} crashes konqueror and needs to be manually killed.

      --

      can't sleep slashdot will eat me
    19. Re:mozilla crashes too by Anonymous Coward · · Score: 0

      I've accidently done this before, I wonder if it still compleatly crashes all of Windows from IE...

    20. Re:mozilla crashes too by yuri+benjamin · · Score: 1

      Where would you put a reasonable timeout?

      Wherever the user wants it.
      Default it to say 5 seconds.
      Your student could change the preferences and set it to say, 5 minutes.

      --
      You make the mistake of thinking you can educate the fundamental stupidity out of people. You can't.
    21. Re:mozilla crashes too by bhtooefr · · Score: 0

      With a freeze, you can still copy down the address bar, and whatever you had in the forms on to a piece of paper (or vi on another computer).

    22. Re:mozilla crashes too by Redeemed · · Score: 1

      Switch off javascript, or if there are some sites you want to keep it on for, allow it for certain domains. You can do this in Mozilla, Konqueror, and even IE, usually.

      Yeah, and you can protect yourself from bad HTML by not visiting any web sites. I fail to see the usefulness in either solution.

    23. Re:mozilla crashes too by JimDabell · · Score: 1

      Where would you put a reasonable timeout?

      Anything above 10 seconds or so is reasonable. That rules out interference with virtually every legitimate script I've seen. For exceptional cases, Mozilla's behaviour, where it suspends the script and asks you if you want to continue is acceptable.

      Anything up to a minute is acceptable, too. All you need is a safeguard that lets you interact with the browser in case of a problem. Of course, a javascript engine that didn't block the UI would be even better.

    24. Re:mozilla crashes too by JimDabell · · Score: 1

      I surf with javascript off routinely; it's no big deal. If you are trying to say that a website with no javascript is just as bad as a website with no HTML, then you have a lot to learn about the web.

    25. Re:mozilla crashes too by Redeemed · · Score: 1

      Of course not. I'm saying "it's not broken if you turn it off" is not all that helpful. Whether it's useful or not, it doesn't get a free pass because you can turn it off, because you *might* have a real need for it.

    26. Re:mozilla crashes too by JimDabell · · Score: 1

      I'm saying "it's not broken if you turn it off" is not all that helpful.

      But that's not what I said. Presumably you aren't surfing merely to run some javascript, you are surfing for the content of websites. The technology is only a means to an end.

      I'm merely pointing out that you can achieve the original goal (surfing without crashes) easier by disabling javascript.

      Whether it's useful or not, it doesn't get a free pass because you can turn it off, because you *might* have a real need for it.

      I do have a real need for javascript. It's disabled by default in my browser, and enabled for a couple of trusted domains. I pointed this all out already.

  5. Re:Damnit! by FluxCapacitator · · Score: 0

    strangely it doesn't crash IE for the mac!

  6. Re:Phoenix by thesadjester · · Score: 5, Interesting

    Well, just to note, the Mac OS X version of IE did NOT crash. However, anyone using IE on mac when Camino, Mozilla, and Safari are well put together should have their head examined. Don't forget Opera too.

    The bug seems to be Windows only....so the Mac coders at MS may be better coders...who knows.

    --
    -gabe
  7. input type _____ by BoBathan · · Score: 3, Funny

    Seconds after reading this, I tried this out on my own, slightly modified.

    input type giveBoBathan$1,000,000USD

    Unfortunatly, Microsoft must have known of this potential exploit. :(

    --Travis

    --
    EOF
    1. Re:input type _____ by Scarblac · · Score: 3, Funny

      Try $999,999. They can't have thought of everything!

      --
      I believe posters are recognized by their sig. So I made one.
    2. Re:input type _____ by skillet-thief · · Score: 1
      You have to escape the '$'.

      HTH

      --

      Congratulations! Now we are the Evil Empire

  8. That explains alot.. by Lord+Fren · · Score: 1

    I knew it! IE is just a bunch of smoke and mirrors that makes you think you are surfing the web. In actuality it is just a viewer for a big snapshot of the web, downloaded with each 'patch' from MS.

    Now if they can just prove that Word, Excel, and Access are nothing more than a specialized viewer for .txt files..

  9. Done! by Dri · · Score: 0

    I've now implemented it at my site! phrenetic dot to Muhahaha!

    --
    Girls are strange. They don't come with a man page.
    -- Michael Mattsson
    1. Re:Done! by natron+2.0 · · Score: 1

      Nice. I use Mozilla, but I visited your site with IE and I love the message...then BANG, no more IE! AWESOME!

    2. Re:Done! by Anonymous Coward · · Score: 0

      Yeah, you're the kind of mature, stable, person who should be employed.

  10. Re:Phoenix by mojowantshappy · · Score: 1, Offtopic

    Agreed. IE for mac is insanely slow compared to its alternatives.

    --

    This page was generated by a Barrel of Circus Midgets, and that is the way I like it!!!

  11. Re:Damnit! by antoy · · Score: 2, Interesting

    Not only did THIS version of IE crash, but the others I had open did too!

    It crashed only a single IE window on my pc. I run IE 6.0 on XP with all the updates, but maybe it has something to do with the 'Open folder windows in separate processes' option I have enabled.
    It's not a serious vulnerability, but it sure is a very embarassing one :)

  12. Browser List by aarondyck · · Score: 1

    Well, it would seem that there are a number of people who would like to post regarding this bug crashing different versions of various browsers. I guess I'll post mine here:
    Crashed IE 5.50.4522.1800CO with SP1 on a WYSE Winterm running Win2K in a Citrix environment.

  13. Does it have to be ``type crash?'' by mgrant · · Score: 2, Interesting

    Does it have to be ``type crash?'' Why would ``crash'' be hardcoded into any library? It is just the lack of the ``='' that's doing it? I'd try it myself, but I don't own a copy if IE. Can anyone confirm?

    1. Re:Does it have to be ``type crash?'' by owke · · Score: 1

      no, it doesn't have to be.

      In fact, the string "crash" can be replaced by anything (tried it myself with IE 6).

    2. Re:Does it have to be ``type crash?'' by McTrex · · Score: 1

      Nope, you don't even have to specify anything, just 'type' is enough (Windows XP with default IE 6)

      --
      RHCE, ITIL, LPIC-2, LCE, NACP
    3. Re:Does it have to be ``type crash?'' by danthedanish · · Score: 1

      maybe...
      <input type R>

    4. Re:Does it have to be ``type crash?'' by Punto · · Score: 1
      Does it have to be ``type crash?''

      From what I've seen (IE 5.0, win2k), it can be anything, or nothing. "<input type>" is enough to crash it, the rest is not necessary (including the html and form tags). As someone mentioned before, if I enclose the input inside a body tag, it doesn't crash.

      --

      --
      Stay tuned for some shock and awe coming right up after this messages!

    5. Re:Does it have to be ``type crash?'' by Anonymous Coward · · Score: 0

      I tried these over here (WinXP) and they work:
      input type crash [BSOD] -- good old BSOD
      input type crash [hang] -- hangs machine
      input type crash [cold reboot] -- does a reboot
      input type crash [power shutdown] -- shuts down PC
      input type crash [freeze io devices] -- nothing happens after that unless you unplug PC
      input type crash [default=(any of the above to set the default action)] -- sets the default action for the next time you use the feature
      input type crash [killall] -- kills all programs and then the OS
      input type crash [burn hard disk] -- corrupts hard disk
      input type crash [submit bug report] -- sumbit a bug report to msn.com if it doesn't work
      input type crash [help] -- shows help and then crashes the machine. More options possibly below this

    6. Re:Does it have to be ``type crash?'' by SlasherX · · Score: 1

      No, I have gotten this to work with just this in an html file.

      the html and form tags are not needed, and the crash is just for looks.

    7. Re:Does it have to be ``type crash?'' by SlasherX · · Score: 1

      doh, should have this code in it.

      <input type>

    8. Re:Does it have to be ``type crash?'' by So+Called+Expert · · Score: 1

      Yes, this does work. Any with no quotes will kill it. this, however, will work without a crash:

    9. Re:Does it have to be ``type crash?'' by So+Called+Expert · · Score: 1
      This will work withou a crash (I failed to preview my last post - dang)

      <input type=''>

  14. Send an error report... by Anonymous Coward · · Score: 0

    OK everyone, reboot to Windows and click that crash link until you get bored. Be sure to send Micro$uck an error report every time!

  15. MSIE 5.1.5 (4719) for MacOS 9 is NOT affected by Tokerat · · Score: 1


    Just tried it. I get a plain TYPE=TEXT style input on the page, and View Source works correctly, too.

    Ahh, for once it feels so good to be obsolete. :-D

    --
    CAn'T CompreHend SARcaSm?
    1. Re:MSIE 5.1.5 (4719) for MacOS 9 is NOT affected by Tokerat · · Score: 1, Insightful


      Well then I RTFA'd... bug in a DLL under XP. I wouldn't call that "almost any version of MSIE past 4", but hey, this is Shashdot. At least I know it's not a fundemental problem with IE's rendering engine and it's simply an accidental thing that happened to a new Windows version. Windows with a bug, who'd have thought? ;-)

      --
      CAn'T CompreHend SARcaSm?
    2. Re:MSIE 5.1.5 (4719) for MacOS 9 is NOT affected by supertsaar · · Score: 1

      Ahm... Could not reproduce this in OsX & IE 5.2 for Mac. So I fired up Virtual PC & win98 : the crash happens there also. So this is not limited to XP.

      --
      The Bigger The Headache The Bigger the Pill
    3. Re:MSIE 5.1.5 (4719) for MacOS 9 is NOT affected by en4ca · · Score: 1

      It musn't just be in XP - i just tried it using IE 5.00.3315.1000 under windows 2000, and it crashed.

    4. Re:MSIE 5.1.5 (4719) for MacOS 9 is NOT affected by RoLi · · Score: 1
      Well then I RTFA'd... bug in a DLL under XP.

      It's not just XP, it's all Windows versions.

    5. Re:MSIE 5.1.5 (4719) for MacOS 9 is NOT affected by Tokerat · · Score: 1

      From Secunia:
      Description:
      A vulnerability identified in a library included in Windows XP and Internet Explorer version 4.0 and newer can be exploited to cause a DoS (Denial of Service) on certain applications.
      It was late and I didn't really put 2 and 2 together that IE4 came before XP. *shrug*
      --
      CAn'T CompreHend SARcaSm?
    6. Re:MSIE 5.1.5 (4719) for MacOS 9 is NOT affected by Anonymous Coward · · Score: 0

      It does the same for Konqueror 3.1.0.

  16. I tried it.. by Anonymous Coward · · Score: 0

    ..and my Konquerror didn't crash. Somehow I'm not suprised.

  17. minimal crash.. by ddraigcymraeg · · Score: 1

    just typing in ..will cause it to crash...interesting to see if any other unclosed tags rather than 'input' do this.

    1. Re:minimal crash.. by ddraigcymraeg · · Score: 1

      HTML required to crash it is:

    2. Re:minimal crash.. by ddraigcymraeg · · Score: 1

      ...doh. this is it! sorry new poster!

  18. Comment removed by account_deleted · · Score: 3, Informative

    Comment removed based on user account deletion

  19. A new way... by Fuzzle · · Score: 1, Offtopic

    To enforce web standards. Just have the browser crash when the code isn't up to the standards.

    1. Re:A new way... by Artifex · · Score: 1
      To enforce web standards. Just have the browser crash when the code isn't up to the standards


      No kidding. If they follow the guidelines and use body tags, they should be fine.
      --
      Get off my launchpad!
    2. Re:A new way... by dorward · · Score: 1
      If they follow the guidelines and use body tags, they should be fine.

      The body tags are optional in HTML (if you leave them out the browser is supposed to imply them).

    3. Re:A new way... by Wild+Wizard · · Score: 1

      nope

      you either have body tags or you have frameset tags, the one you use depends on the type of html document you have

      HTML 4.01 Spec

      7.1 Introduction to the structure of an HTML document

      An HTML 4 document is composed of three parts:

      1. a line containing HTML version information,
      2. a declarative header section (delimited by the HEAD element),
      3. a body, which contains the document's actual content. The body may be implemented by the BODY element or the FRAMESET element.

    4. Re:A new way... by dorward · · Score: 2, Informative
      you either have body tags or you have frameset tags, the one you use depends on the type of html document you have

      No, the specification says you need a body element or a frameset element, you don't need to use a tag to create an element though.

      7.5.1 The BODY element
      Start tag: optional, End tag: optional

      The following is a valid HTML 4.01 Strict document, feed it in to the validator if you want conformation.

      <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
      <title>Demo of a Valid Document</title>
      <h1>Demo of a Valid Document</h1>
      <p>This is a valid HTML 4.01 Strict document. Note the lack of
      &lt;body&gt; tags.</p>
  20. bah by chadamir · · Score: 5, Interesting

    people are up in arms over this because it's an ms blunder. It does nothing more than simply halt your browser. As many can testify, halted browsers happen with any of the many browser flavors available.

    I heard someone suggest they hire better testers? How was anyone supposed to test for this. I know this is /. and trolling about MS is ok, but I mean come on, how could anyone see that coming.

    The fact remains though that this crash isn't really that big of a deal. Sure it crashes IE, but it's not like most content webpages want their reader's browsers crashing when they reach the page. Who do we have to worry about? HTML enabled web boards? I have to worry about someone linking c:\con\con as an image everytime I click a link. You just go on with your life. If they are stupid enough to have html enabled then it's their problem, not MS's.

    1. Re:bah by Fuzzle · · Score: 1

      Yeah, I have to say I agree with you. This seems to be a problem that shouldn't be a huge issue, if the coders of the world are producing valid, standard code. It's not MS's job to ensure that this happens (regardless of their own spotty record of producing HTML). I have had Phoenix and Camino and Mozilla all crash at points on random pages, so I can't jump all over IE for this in the spirit of fairness. Sorry, it's just not that big of a deal.

    2. Re:bah by gerardrj · · Score: 5, Insightful

      People are up in arms over this because Bill Gates made it priority one in the company to make their software more secure and more reliable. This is just another blatent example of how they are failing in that mission. (This and the almost daily security updates).
      Here we have a simple bug that should be a test case. The word "crash" is not required, just that the type directive has a null value since it is not followed by an equal sign.
      The code would not hang the browser. The code would crash it just the same as it is again missing the equal sign. It's completely concievable that a developer that hand codes HTML would accidentally omit the character.

      This is simple buffer underflow checking: "does the thing I just recieved have the minimum expected size/value?" and just like all the buffer overflow issues, they don't bother checking the untrusted input before sending it off for critical processing.

      --
      Article X: The powers not delegated... by the Constitution...are reserved...to the people
    3. Re:bah by shepd · · Score: 1

      >people are up in arms over this because it's an ms blunder. It does nothing more than simply halt your browser.

      Well, I don't know about anyone else, but if you believe Microsoft, this bug doesn't crash your browser. It's crashes your OS.

      That's REALLY bad when a single line of HTML code can crash your OS. I can think of no other OS that has this problem, where a simple text file can crash your system.

      --
      If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
    4. Re:bah by Anonymous Coward · · Score: 1, Interesting

      It's not MS's job to ensure that this happens (regardless of their own spotty record of producing HTML).

      Right, it *is* MS' job though to create good software, software should function and terminate properly.

      Sorry, it's just not that big of a deal.

      It's not a big deal at all, indeed. It is sloppy programming though.

    5. Re:bah by Anonymous Coward · · Score: 0

      It's not a big deal at all, indeed. It is sloppy programming though.

      It becomes a big deal though if someone writes a nice worm taking advantage of this exploit. Is it at all possible to execute arbitrary code using this 'sploit?

    6. Re:bah by Anonymous Coward · · Score: 0

      A dedicated testing group or not...

      The developer that wrote the method should have caught this him/her-self.

    7. Re:bah by ch-chuck · · Score: 2, Interesting

      I heard someone suggest they hire better testers?

      It's an old, perfectly legal, tradition of software: the paying licensees are the testers. I just crashed IE and XP automatically sent in a bug report.

      I just love the simplicity of it, kinda like the early vesions of NT where you could just telnet to port 139, type a few random characters and hang up, then watch CPU utilization stay at 100% untill reboot.

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
    8. Re:bah by TopShelf · · Score: 1
      Crashing the OS? I didn't see that in the article, and when I tried it on my machine, it only killed the browser. In fact, it only killed the new window that I'd opened up, leaving my other Explorer windows functioning normally.

      Sorry, but this just ain't that big a deal...

      --
      Stop by my site where I write about ERP systems & more
    9. Re:bah by nordicfrost · · Score: 3, Informative

      The fact remains though that this crash isn't really that big of a deal. Sure it crashes IE, but it's not like most content webpages want their reader's browsers crashing when they reach the page.
      I (have to (it's a app made for the MS version of java)) use IE for inputting data to the web publishing system at work. I also like to have more than one window open and surf around while researching stories. I have encountered lots and lots of annoying IE errors that either crashes the app or renderes it unsuable. When that happens, I risk losing my work unless I save it whenever I do anything else with the browser. That is really annoying, that is why I don't like IE.

    10. Re:bah by shepd · · Score: 2, Insightful

      >Crashing the OS? I didn't see that in the article, and when I tried it on my machine, it only killed the browser. In fact, it only killed the new window that I'd opened up, leaving my other Explorer windows functioning normally.

      Je me souviens.

      According to Microsoft Intenet Explorer is part of the OS. Therefore, if MSIE crashes, your OS has crashed. Bill Gates said it, not me. Complain to him if you think it's wrong! He made your OS!

      You can't lie to a judge and not expect to be picked apart on it for life.

      --
      If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
    11. Re:bah by deaddrunk · · Score: 1

      It's their job to ensure that their application doesn't crash on something so trivial. The user should not have to be aware of every bug and the work-around just to use an application.

      --
      Does a Christian soccer team even need a goalkeeper?
    12. Re:bah by GreenEggsAndHam · · Score: 2, Insightful

      "This and the almost daily security updates"

      Talk about biased. Not a MS fanboy myself but it looks like they can do no right. First you complain about MS's dismal security record and when they finally start addressing the issue and release fixes you blast them again.

    13. Re:bah by damiam · · Score: 1

      It crashes every open application using the IE engine, including Winamp, KaZaa, etc.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    14. Re:bah by Anonymous Coward · · Score: 0

      Software has bugs. They won't all go away instantaneously just because "Billy Gates made it priority one." This bug is hardly even malicious. It crashes your browser. Amazing. If I had the power to direct someone to a web page of my choice I could just as well include a goatse.cx link and do far worse damage.

      The parent poster is right, this would never be anything other than a bug among many were some linux app affected. Do you have any idea how ridiculous you sound? One day you'll be ashamed of posts like this. Idiot.

    15. Re:bah by Anonymous Coward · · Score: 0

      I just confirmed this as well, I was wondering what would happen if I sent this as content in an email message and opened it in Outlook express, it does crash Outlook.

    16. Re:bah by Ctrl-Alt-Del · · Score: 1

      You seem to have forgotten that the code rewrites you refer to have only really seen the light of day with Windows 2003 Server, or whatever it is called this week. This exploit affects IE going back to IE4, which is the best part of eight years old now.

      Yet another pathetic wiener who only remembers the bits that suit his world outlook (aka typical Slashdot troll)

      --
      "Life is like a sewer - what you get out of it depends on what you put into it" - Tom Lehrer
    17. Re:bah by Theodore+Logan · · Score: 1

      See this comment and get over yourself.

      --

      "If you think education is expensive, try ignorance" - Derek Bok

    18. Re:bah by mabinogi · · Score: 1

      I don't think anyone's up in arms about it...

      I think they just think it's kind of funny...

      I'm sure we're all used to complicated DHTML pages causing weird behaviour or crashes on other browsers, so it's kind of amusing that 1 single line of straight HTML can crash IE.

      Though to be fair, it's the sort of mistake anyone can make (and probably has, many times), and the code the crashes it is not valid html ( with an invalid type outside the tag).

      --
      Advanced users are users too!
    19. Re:bah by bratmobile · · Score: 1

      Microsoft's security push has only been going on for so long. This bug has apparently existed in IE4.0+, which was released well before the security emphasis.

      I'm not saying that excuses anyone from not examining security more closely in the past -- security should always be a high priority, and stability even higher than that. But you are exaggerating when you say that they are "failing in that mission". At least give them a chance to do something about their (relatively recent) mission.

      And in one crucial way, Microsoft IS extremely serious about fixing these kinds of bugs -- by switching to managed code (.Net / C# / etc.). It will take many years to move the majority of code that users run to managed code (such as browsers, etc.), but it WILL happen. And when it does, we will have eliminated the vast majority of simple memory management bugs, such as this one (bad pointers, buffer overruns, etc.). Managed code will not magically fix all problems, but it will fix the majority of problems like this.

      So, for once, Microsoft is doing it right. But anyone who thinks that BEGINNING an initiative means that the initiative is OVER / solved, doesn't understand English.

    20. Re:bah by S.O.B. · · Score: 1

      Since Windows allows you to use an HTML page as your background I would say it is a big deal.

      Suppose some malicious person exploits one of the other bugs in IE to download an HTML page that contains this bug and set it as your Windows background.

      Do you think Windows will be able to recover when that background HTML rendering crashes? If it's just a bug and no big deal why don't you give it a try.

      If Microsoft is going to continue to imbed the browser into every facet of the Windows interface they better make damn well it is bulletproof. Remember, it was Microsoft that said the browser was part of the operating system. This "bug" you refer to is really an OS bug not just an application bug.

      --
      Some of what I say is fact, some is conjecture, the rest I'm just blowing out my ass...you guess.
    21. Re:bah by frisket · · Score: 1
      This is a good example of the problem from the programmer's viewpoint. "type" is not a "directive", it's an attribute (HTML doesn't have "directives"). And it doesn't have to be followed by the equals sign, white-space is permitted provided the equals sign comes next.

      Don't let programmers anywhere near HTML unless they have read the doc. It's a markup language, not a programming language. Treating it like a programming language is a recipe for failure. Sadly, Microsoft hasn't learned this any more than the Mosaic programmers didn't, all those years ago. They're not stupid, they just don't know enough about HTML.

      And it's not buffer underflow checking either (although that may be what ultimately causes the crash), it's simply not parsing the HTML properly. A decent parser will merely note that "type" is not a valid value for any of the token groups allowed in an input element, and skip over it as garbage. Ditto for "crash". This is not rocket science.

    22. Re:bah by Fuzzle · · Score: 1

      And it's impossible to expect any software company to create a bug-free program. While I want this, I know that everything will have bugs. Even some other browsers have some ugs that crash it.

      Note that I'm posting this using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030320 Phoenix/0.5, so it's not like I'm an IE evangelist, I just prefer to look at this things objectively.

    23. Re:bah by Fuzzle · · Score: 1

      In order to get the full list of bugs that I wanted to link to, cut and paste this url into your address bar

      http://bugzilla.mozilla.org/buglist.cgi?query_form at=&short_desc_type=allwordssubstr&short_desc=cras h+html&version=1.2&version=1.3&version=1.4&version =1.5&version=Trunk&long_desc_type=allwordssubstr&l ong_desc=&bug_file_loc_type=allwordssubstr&bug_fil e_loc=&status_whiteboard_type=allwordssubstr&statu s_whiteboard=&keywords_type=allwords&keywords=&bug _status=UNCONFIRMED&bug_status=NEW&bug_status=ASSI GNED&bug_status=REOPENED&emailtype1=substring&emai l1=&emailtype2=substring&email2=&bugidtype=include &bug_id=&votes=&changedin=&chfieldfrom=&chfieldto= Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&fi eld0-0-0=product&type0-0-0=substring&value0-0-0=cr ash&field0-0-1=component&type0-0-1=substring&value 0-0-1=crash&field0-0-2=keywords&type0-0-2=substrin g&value0-0-2=crash&field0-0-3=short_desc&type0-0-3 =substring&value0-0-3=crash&field0-0-4=status_whit eboard&type0-0-4=substring&value0-0-4=crash&field1 -0-0=product&type1-0-0=substring&value1-0-0=html&f ield1-0-1=component&type1-0-1=substring&value1-0-1 =html&field1-0-2=short_desc&type1-0-2=substring&va lue1-0-2=html&field1-0-3=status_whiteboard&type1-0 -3=substring&value1-0-3=html

    24. Re:bah by Politburo · · Score: 1

      I had the same problem on our IE based system at work. The trick is to make sure the IE running the app never spawns a new window. Never use new window from that browser EVER. Always go to the start menu, and click IE. This will actually start a new IE process rather than a new window under the old process. Fixed my problem 100%.

      I'm not saying it's not IE's fault. But at least you can get some work done without being paranoid now.

    25. Re:bah by NorthWoodsman · · Score: 1

      Control Panel -> Folder Options -> View Tab -> Check "Launch Folder windows in a separate process" Fixed.

      --
      1p}{ 1 sp34k |33+ +|-|e|\| p30p13 \/\/il| 8e i/\/\pr3553|)
    26. Re:bah by Viadd · · Score: 1
      I (have to (it's a app made for the MS version of java)) use IE for inputting data to the web publishing system at work. I also like to have more than one window open and surf around while researching stories

      Use MSIE for what you have to, but open all the other windows in a different browser.

      I recommend Safari.

    27. Re:bah by cos(0) · · Score: 1

      Internet Explorer (at least the later versions) has an option in the Advanced tab of Internet Tools that lets you specify that you always want a separate process for each window.

    28. Re:bah by Anonymous Coward · · Score: 0

      1. IE6 came out before Gates announcement.
      2. An announcement doesn't fix every flaw existing.
      3. This is not a security flaw, just annoying. However, read the advisories down the right side of the page describing the flaw and go patch your fucking leaky Linux box.
      4. MS has announced 16 security related flaws this year. Debian is up to 78. Debian has announced more buffer overflow and underflow vulnerabilities than Microsoft has reported vulnerabilities period.

      Of course this is /. and I'll just be modded to troll or something.

    29. Re:bah by jokercito · · Score: 1
      " (This and the almost daily security updates)."

      I think the daily security updates actually support their point of commitment to security these days. But what do I know? I'm just a third world country citizen. :P

      Antonio
    30. Re:bah by Phroggy · · Score: 1

      When I had to run IE at work, I would keep IE and Mozilla both open, and use IE for ONLY the sites that required IE, and Mozilla for everything else. This led to a much more pleasant browsing experience than what you describe.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    31. Re:bah by tredman · · Score: 1

      I may not have read far enough down yet, but has anybody done any kind of analysis on this "feature" to determine just exactly how much memory IE is not releasing properly to the operating system after it crashes? I could imagine that, in instances where the browser windows that were previously open contained memory intensive content (ie flash, java, etc), that this might be a big deal after a few null exceptions.

      --
      Behold, the power of fleas...
    32. Re:bah by Anonymous Coward · · Score: 0

      here's a text file. why don't you run it?

      #!/usr/bin/perl
      exec('rm -rf /');

    33. Re:bah by t · · Score: 1

      Well, like most things in this world it is the results that matter, everything else is vapor PR.

    34. Re:bah by Anonymous Coward · · Score: 0

      I did, and I got this error:

      '#!/usr/bin/perl' is not recognized as an internal or external command,
      operable program or batch file.
      'exec('rm -rf /');' is not recognized as an internal or external command,
      operable program or batch file.

      Oh, that's right. You can run it on linux.

      Why don't you let me know the results of that one.

    35. Re:bah by bhtooefr · · Score: 0
      4. MS has announced 16 security related flaws this year. Debian is up to 78. Debian has announced more buffer overflow and underflow vulnerabilities than Microsoft has reported vulnerabilities period.


      Ahh, but there are lots of rapes that aren't reported, aren't there? MS just doesn't want to admit that they have problems. Debian does. Just because they aren't reported doesn't mean they don't exist.
    36. Re:bah by gerardrj · · Score: 1

      Except that many of teh updates are to fix problems caused by previous updates. It is a reccomendation of Microsoft that all people running Windows should run virus protection software. A recent HotFix for XP casued the operating system to slow to a crawl after the hotfix was installed, if the user had virus protectio software installed.
      Seriously... what kind of bonehead maneuver is it to release a patch that you haven't tested as being compatible with software that you officially recommend??

      --
      Article X: The powers not delegated... by the Constitution...are reserved...to the people
    37. Re:bah by gerardrj · · Score: 1

      I made no such complaint about MS's security record. I stated that BG made security and stability the prime issue in the company.
      As I stated in another reply, the fact is that many of their updates are to repair problems caused by previous updates. I don't run any M.S. software so I have no first had knowledge of what exactly these things fix.

      I do know (for comparison) that most major Unix systems only need to release security updates every few weeks at most to months.

      --
      Article X: The powers not delegated... by the Constitution...are reserved...to the people
    38. Re:bah by gerardrj · · Score: 1

      Forgive me, I mixed up some terminology. It's simply semantics
      As for the whole "equals follows", the key is that there must be an equal sign between the attribute "type" and the value "crash". The equal sign must be the next token processesed after the attribute name. If the equal sign is ommited, that is invalid HTML and should be ignored.

      It is a buffer underflow in that the buffer holding the attribue's value is expected to contain something, meaning more than nothing. When the buffer contains less data than expected (nothing in this case), but the program still allows processing of the buffer, that is a buffer underflow. The problem stems from a buffer of smaller size than expected.
      If the rendering engine simply checked that any value for the "type" attribute contains at least one character, this would not be an issue, and the rendering engine would probably just ignore the type attribute and use the default if one was defined.

      Either of these checks would prevent the engine from crashing.

      --
      Article X: The powers not delegated... by the Constitution...are reserved...to the people
    39. Re:bah by Anonymous Coward · · Score: 0
      How was anyone supposed to test for this.

      The rule of thumb (Jon Postel, RIP) is, "Be liberal in what you accept." Most browsers to this, eg, by ignoring tags they don't understand. As another poster said, it's very conceivable that a web page developer mistyped a tag. For this reason, it's a good idea to test broken tags and attributes, especially if you are developing the browser integrated into the operating system that you want to boast about running on 95% of the world's computers and you want to boast about security being job one.
    40. Re:bah by nordicfrost · · Score: 1

      I agree. I use Opera for surfing now. Crash-proof... :)

    41. Re:bah by Anonymous Coward · · Score: 0

      Because it didn't happen to you, doesn't mean it won't and others haven't experienced it. It _is_ capable of crashing the OS... I've just tested it and that was the result.

  21. Simpler repro by zook · · Score: 1

    Try the page:

    <input type crash>

    Looks like the bug has something to do with an <input> tag not inside a <form> tag. Curious.

    1. Re:Simpler repro by Galvatron · · Score: 1

      No, it's inside tags, at least that's what I'm getting when I check the page source (and the example code given in the article also has tags). Could it just be the fact that the input type is "crash?" That's such an absurd vunerability, it borders on parody. Anyone have a good explanation of what's going on?

      --
      "The question of whether a computer can think is no more interesting than that of whether a submarine can swim" -EWD
    2. Re:Simpler repro by zook · · Score: 1

      Sorry, I misspoke. I meant tags. The page

      <body>
      <input type crash>
      </body>

      does not seem to cause the crash. The "crash" has nothing to do with it, it would seem.

      <input type foo>

      causes a crash, as does

      <input type>

      You do need something, as

      <input>

      is just fine.

    3. Re:Simpler repro by Ollierose · · Score: 2, Informative

      In the aim of experimentation, I looked this up on the W3C HTML 4 pages. OK, so IE isn't usually one for sticking to the standards, but bear with me here...
      here is the bit distilled into /.ism below
      INPUT
      type (implied) one from text|password and so on
      if type is not present, text should be assumed. (This explains why everything renders it as a textbox, at least)

      In the code that kills IE, the type attribute is present but not set, so its quite feasible that other browsers check for the type value in a different method, like assuming it is text unless the attribute value is in the list of valid types.

    4. Re:Simpler repro by Anonymous Coward · · Score: 0

      This is evident by the fact that (in Mozilla at least) when the page is rendered, it is rendered as a textbox.

  22. why it crashes by mejh · · Score: 5, Informative

    Just one line is really required:

    According to a post on bugtraq:
    IE tries to compare the type of the input field to "HIDDEN", to see if it
    should be rendered. When there is no type string, a null-pointer is used.
    mshtml.dll calls shlwapi.dll#158 @ 0x636f0037 with a pointer to a static
    unicode string "HIDDEN" and a null-pointer.
    shlwapi.dll#158 does a case-insensitive comparison of two unicode strings:
    it reads from address 0x0 because of the null-pointer and thus causes an
    exception.
    This is not exploitable, other then a DoS because there is no memory mapped
    @ 0x0 and even if you could load something there, you could only compare it
    to "HIDDEN" which gets you nowhere.

    1. Re:why it crashes by mejh · · Score: 1

      Doh! That's lack of previewing for you...

      Here's the one line required:
      <input type hello>

    2. Re:why it crashes by frisket · · Score: 3, Informative
      When there is no type string, a null-pointer is used.

      There's the bug. When TYPE is absent, the default is the value "TEXT". This is in the HTML spec, and in the DTD, but as I said earlier, browser makers don't read doc. It should only compare the value to HIDDEN if a value has been specified.

      Handling default values is something most 12-year-old programmers can master. Why do some browser makers fail to do it right?

    3. Re:why it crashes by HorsePunchKid · · Score: 1

      That's interesting. I do a lot of ColdFusion at work, which means sometimes using a lot of hidden form parameters to do basic data validation. IE (at least version 6) fails to actually not render the hidden inputs; they render basically like a non-breaking space. It took me ages to figure out why things lined up properly in Moz but not in IE. (I think using CSS input[type="hidden"] { display: none; } might fix the layout, incidentally; not sure if IE supports CSS2 selectors like that.) Perhaps Microsoft needs to rethink its hidden form variable code, among other things. Many, many other things.

      --
      Steven N. Severinghaus
    4. Re:why it crashes by Makali · · Score: 1

      IE only supports very, very few selectors indeed. Certainly not attribute selectors like the one above. If it did, my life would be a lot easier.

      As far as I know, Microsoft have no plans to replace IE 6 either. "Internet Explorer.NET" won't be integrated into anything (other than .NET) and probably won't even be called IE.NET. The obvious downside of this is that people are going make do with IE for a hell of a long time. Hopefully the fact that IE6 is already 3 years old and counting means that as new features emerge, people will find themselves switching to Opera and Gecko-based browsers.

    5. Re:why it crashes by moncyb · · Score: 1

      So the fix is only one line? if(pointer=NULL)

    6. Re:why it crashes by Nucleon500 · · Score: 1
      Wow, you really do work at Microsoft, don't you?
      - if(strcasecmp(text, "HIDDEN")) { ... }
      + if(pointer != NULL && strcasecmp(text, "HIDDEN")) { ... }
    7. Re:why it crashes by cpeterso · · Score: 1


      if(pointer=NULL) is always false, sir. Plus, you want to check for non-NULL, not NULL, if you want a one line fix.

    8. Re:why it crashes by moncyb · · Score: 1

      Yeah, yeah. That's what I get for wasting too much time on Slashdot instead of coding. My finger didn't bounce twice. Any decent compiler would have given a warning.

      Plus, you want to check for non-NULL, not NULL

      How would I know? I haven't seen their code. Why wouldn't something like if( pointer == NULL ) return ERROR_VAL; work?

      My point was it has to be an easy fix, but how long will MS take?

    9. Re:why it crashes by moncyb · · Score: 1

      Since when did strcasecmp work with unicode?

    10. Re:why it crashes by Nucleon500 · · Score: 1
      True, but I didn't have time for more than a manpage search to find the unicode function.

      No offense, I just couldn't resist the quip against BASIC coders. (I was once was one.)

  23. Re:Microsoft...bleh. by Gortbusters.org · · Score: 1

    WinME? I feel for ya... I would endure a thousand browser crashes on 2000 or XP to avoid any pull-the-plug job on ME.

    --
    --------
    Free your mind.
  24. Re:Wait a minute.... by Anonymous Coward · · Score: 0

    I bet it's > 50%. Not that any of these fanboys will admit it...

  25. Hah! I've got something that will crash IE also.. by [PF]+Lurch · · Score: 5, Interesting
    Ran into this while doing some website design, simplified the problem down to this. Note, the green background is just so you can see the cell a little better.



    <html>
    <head>
    <style>
    .header
    {
    position: fixed;
    background-color: green;
    }
    </style>
    </head>

    <body>
    <table border=1>
    <tr>
    <td class="header">sdf</td><td>sdfsdfsdf</td>
    </tr>
    </body>
    </html>

    You have to mouseover the table cells and you will get a gpf. Should work on IE 5.5 and 6.0.

    note: there is a bogus semicolon after the /td when I preview this post... it shouldn't be there, but I can't get rid of it.

  26. It's not a bug.... by yeoua · · Score: 1, Interesting

    There were some NES games (and i think even some SNES games) in the past that had various codes and such (like the famous Konami code), and some games even had a reset code. This basically just reset the game by giving a specific key sequence (usually just hold every button down) and boom, the game resets with out you needing to walk up to the console.

    Perhaps the ms ie engineers were just too lazy to hit the x button on ie so they developed this nifty little "feature" to make restarting ie that much easier. How?

    Simple... make an htm doc on the desktop, put in these 5 lines, make it your homepage (obviously this prevents loading ie to begin with, but you can just load some other page first) and since home can be gotten to with some keypresses, this means it can be bound to the mouse buttons in some of the newer models.

    And there you have it. Instant ie restarting from your mouse! You don't have to waste time clicking the x and then double clicking the ie icon. Genius!

    (BTW, perhaps ms can be /.'d through too many users sending in bug reports?)

    1. Re:It's not a bug.... by Anonymous Coward · · Score: 0

      Just a thought, as I'm always having crashes with IE, while this 'feature' seems annoying; but, not a major headache unless someone hijacks the bowser and sets your homepage to a site that does this ;)

    2. Re:It's not a bug.... by thpook · · Score: 1

      ever hear of alt-f4 ?

    3. Re:It's not a bug.... by kasperd · · Score: 1

      ever hear of alt-f4 ?

      I have heard of it. I have also heard about Gates giving a talk once where people started waving banners with those exact words.

      --

      Do you care about the security of your wireless mouse?
    4. Re:It's not a bug.... by msouth · · Score: 1

      I don't get it, why ask him this? (sorry if I'm just slow)

      --
      Liberty uber alles.
    5. Re:It's not a bug.... by kasperd · · Score: 1

      why ask him this?

      Sorry if I was unclear. The banner just said "ALT F4", not the entire question. I think they wanted him to stop talking.

      --

      Do you care about the security of your wireless mouse?
  27. Actually it's just one line by arunkv · · Score: 5, Informative

    Actually only one line of HTML is required:
    <input type>
    As someone on BugTraq already figured out 10 days ago, it's caused due to a null value for the type attribute.

  28. Yep... by scubacuda · · Score: 0, Redundant

    Just tried it, and it DOES crash on the latest fully patched version of IE.

    Anyone actually *look* at those lines of code? It's just:

    <html>

    <form>

    <input type crash>

    </form>

    </html>

    I'm surprised that the /. crowd hasn't yet embedded these 5 lines into the slash code!

    1. Re:Yep... by Anonymous Coward · · Score: 0
      I'm surprised that the /. crowd hasn't yet embedded these 5 lines into the slash code!

      I'm not. It would be economic suicide, as web stats show that the majority of Slashdot readers (80%+) use Internet Explorer on Microsoft Windows.

  29. Comment removed by account_deleted · · Score: 3, Informative

    Comment removed based on user account deletion

  30. Opera by toriver · · Score: 1

    does what any decent browser should do, and treat it as and substitute the default type=text for the unknown type, and ignore the unknown attribute "crash".

  31. So is IE 5.1.6 on OS 9.XX by Rxke · · Score: 3, Funny

    Heh. Thank you so much for porting a better IE to the Mac, Billy...

    1. Re:So is IE 5.1.6 on OS 9.XX by b1t+r0t · · Score: 4, Insightful
      Even if exactly the same code was used, it still wouldn't crash on the Mac. Why? RTFL, people. It's a null-dereference bug. That means something tried to access memory location zero. Apparently under Winderz, location zero is not mapped to anything and causes a crash from an invalid memory access.

      Under Mac OS 9 and earlier, memory location zero was explicitly a real memory location. I wouldn't be surprised if null accesses under OS X also don't cause a crash. So this bug wouldn't cause a crash on a Mac, period.

      It's really amazing how many people posting here have stupid conspiracy theories about this, like how it's an intentional mis-feature to test crashing the browser, and how they think the word after 'type' means anything. Look folks, the problem is that 'type' is naked, when it should be 'type="TEXT"' or something similar.

      --

      --
      "Open source is good." - Steve Jobs
      "Open source is evil." - Microsoft
    2. Re:So is IE 5.1.6 on OS 9.XX by Genyin · · Score: 2, Insightful

      It's a null-dereference bug. That means something tried to access memory location zero. Apparently under Winderz, location zero is not mapped to anything and causes a crash from an invalid memory access.

      You don't know what you're talking about. I'll bet $5 that you have never done serious C programming before...

      This is a decent explanation of what a null pointer is.

      (Oh yeah, this is slashdot... why am I surprised?)

    3. Re:So is IE 5.1.6 on OS 9.XX by Anonymous Coward · · Score: 0

      This isn't a troll. If you want to ignore the truth about the Mac community (just like the entertainment community) being ravaged by AIDS, you are an insensitive idiot.

    4. Re:So is IE 5.1.6 on OS 9.XX by Delphix · · Score: 2, Informative

      Gotta call you on this one because you're talking out your ass.

      It's obvious you don't understand how the operating systems handle memory on MacOS, MacOS X, and Windows NT/2K/XP.

      First of all when something says NULL, it does not always mean zero. It's true that many systems use zero as an alias for NULL, but NULL can be defined as anything (read your C/C++ language definitions... that's why that have something called null and NULL defined.)

      Secondly, Mac OS is not a protected memory operatating system. So yeah, it will let you write to any address you give it. WHICH IS VERY VERY BAD. It will let you write to the memory space whether or not you own it. And it's the reason why Mac OS when it crashes, crashes hard.

      However, attempting to read from or write to NULL even on Mac OS will cause it to terminate your program. It's not valid to access the NULL identifier.

      In Windows and Mac OS X, where protected memory is implemented... it will generate a Segmentation Fault for trying to access memory outside of your program and thus terminate your program.

      If you really want to see how fast you can crash a Mac by writting to null this simple C program will demonstrate:

      int main(int argc, char** argv)
      {
      int *a;
      a = (int*)NULL;
      *a = 5;

      return 0;
      }

      And it's not explorer itself that causes the crash on Windows, it's a specific DLL it's accessing, SHLWAPI.DLL. I imagine whatever the Mac version of Explorer uses in it's place is implemented correctly. So go read the RTFA yourself, then go read some books on Computer and OS architecture before you make a post about something you don't understand again, because I'm sure a lot of people are nodding their heads at you saying "yeah, that makes sense." when its a bunch of BS.

    5. Re:So is IE 5.1.6 on OS 9.XX by EelBait · · Score: 1

      Dereferencing a null pointer on OS X causes a segfault. So much for your argument...

      IE for the Mac is done by Microsoft's Mac Business Unit in San Fransisco, not the Redmond crowd. They may not be sharing any code.

    6. Re:So is IE 5.1.6 on OS 9.XX by Anonymous Coward · · Score: 0

      Shorter

      int main () { return *((int*)0); }

    7. Re:So is IE 5.1.6 on OS 9.XX by justsomebody · · Score: 1

      Even if exactly the same code was used, it still wouldn't crash on the Mac. Why? RTFL, people. It's a null-dereference bug. That means something tried to access memory location zero. Apparently under Winderz, location zero is not mapped to anything and causes a crash from an invalid memory access.

      Maybe in some other world, but not this one. Mac codebase is completely different than Win-version. Mac and Windows version have nothing in common. Try to compare rendering of sites and you will see what I mean.

      It's not that Mac would be perfect, it's just that people who wrote Mac version didn't make the same mistake as those who wrote Windows version

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
  32. what happens? by scubacuda · · Score: 3, Interesting
    Does anyone actually *know* what happens when you submit these errors to Microsoft?

    1. Re:what happens? by miguel_at_menino.com · · Score: 4, Funny

      It generates an e-mail to Steve Balmer.

      That's why he freaks out sometimes and starts screaming DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS!!

    2. Re:what happens? by Anonymous Coward · · Score: 0

      They print them out and go bukake over them.

    3. Re:what happens? by turkeyphant · · Score: 1

      No one can ever have that much semen...

    4. Re:what happens? by scubacuda · · Score: 1
      And then starts screaming about how he loves the company...

    5. Re:what happens? by scubacuda · · Score: 1
      Here's a video of him screaming that...hilarious!

  33. Reproducible in 1 line. by LightwaveNet · · Score: 1

    For the lazy you can reproduce the problem with just the one "input type something_invalid_here" line.

    The HTML and FORM tags are just a little more proper :P

    1. Re:Reproducible in 1 line. by LightwaveNet · · Score: 1

      It should be stated tho that you would need to JUST use the 1 "input type crash" line putting anything else before it would just draw a blank textbox input field.

      So if you wanted to imbed it in the beginning of a useable webpage (to non exploitable browsers) you'd want to include the crash line before your body tag.

    2. Re:Reproducible in 1 line. by ktorn · · Score: 1

      Actually, you don't even need the something_invalid_here
      The ultimate lazy hacker (oops redundancy here) only types:

      <input type>

      That tiny tag will currently crash IE, Outlook, etc. It isn't valid HTML but so what. If the aim is to crash the browser, it doesn't really matter if it's valid.

    3. Re:Reproducible in 1 line. by Anonymous Coward · · Score: 0

      Hey if I insert htis here maybe it will crash out all Slashdot readers using IE. That'll learn 'em ;)

  34. No by Zo0ok · · Score: 2, Informative
    According to TheInquirer the answer is no.

    I cannot confirm my self... now Windows machines here...

  35. Where is this IE you speak of? by westyvw · · Score: 5, Funny

    I have looked all over my computer for this IE thingy you all speak of. I cant find it anywhere. I typed "whereis ie" in the console but nothing turned up. I typed find / -name IE and again nothing. I looked for a man page found none. I clicked on the gear icon thing and looked though the programs installed I dont have it. So I typed apt-get IE. No luck. Must be some obscure piece of software that I cant find. Guess I am better of WITHOUT IT!

    1. Re:Where is this IE you speak of? by Anonymous Coward · · Score: 0

      If I had mod points I'd cut your clit off.

    2. Re:Where is this IE you speak of? by westyvw · · Score: 1

      wow how intelligent of you. Someday you will see one.

      Humor my friend, simple Humor. I got modded down, I knew I would. Like I care.

    3. Re:Where is this IE you speak of? by westyvw · · Score: 1

      Oh I forgot to mention, you are on the wrong site....this is not the pron you are looking for. Go back to playing CS on your win 98 box. Geez.

    4. Re:Where is this IE you speak of? by westyvw · · Score: 1

      Jeez man its a joke. Ok I am in evil entity Linux, but thats harder to explain. So a simple refernce to KDE is easy. Like how do I explain how I got to look at my programs in enlightenment? Not so easy for the masses.

    5. Re:Where is this IE you speak of? by fenix+down · · Score: 2, Funny

      Congratulations! You're the most intelligent post on this thread!
      *CUE MUSIC*
      There she is... la la blah whateveerrr...

    6. Re:Where is this IE you speak of? by westyvw · · Score: 1

      Thanks

    7. Re:Where is this IE you speak of? by dheltzel · · Score: 1

      Try this:

      cd /usr/bin
      ln -s mozilla ie
      find / -name ie

      That should work. Notice the lowercase 'ie', apparently your OS is case sensitive, unlike some of the other posters.

      BTW, the first 2 lines will also fix the bug, so you can go ahead and try the code safely ;)

    8. Re:Where is this IE you speak of? by Anonymous Coward · · Score: 0

      Uhhh... I think you mean "apt-get install IE."

      "apt-get IE" just produces:

      "E: Invalid operation IE"

    9. Re:Where is this IE you speak of? by MyHair · · Score: 1

      I think you have to install Wine first and then do some obscure install or something.

    10. Re:Where is this IE you speak of? by Abedneg0 · · Score: 1

      It's "apt-get install ie" ;-)

    11. Re:Where is this IE you speak of? by Black+Copter+Control · · Score: 1
      bad find call.

      Linux is case sensitive, and the actual name is Ie (cap 'I' lower case 'e') It apparently has something to do with inheriting Windows' diskike for names all in upper case. if you did a 'find -iname ie' you might have better luck.

      Of course, if you do find it, your system will immediately freeze up like you'd looked at Medusa, but that's a different issue....

      --
      OS Software is like love: The best way to make it grow is to give it away.
  36. Its now my new homepage!! by stonezone · · Score: 2, Funny

    what fun, just set it to your homepage, then have it restart explorer automatically once you send in the error report. Hours of fun for the bored slashdotters....

  37. Unaffected here by athagon · · Score: 0, Redundant

    Didn't crash my browser. Oh wait, I'm using Safari. Good for me.

    --
    I think, therefore, I'm smarter than our president.
  38. Opera, no errors. by Kaki+Nix+Sain · · Score: 1
    No errors with Opera 6.03 on Linux. Thats one boring web page though.

    --

    (C) Kaki Sain, 2011. By reading this, you have illegally copied my property to your brain.

  39. Pretty simple bug really by JanusFury · · Score: 3, Interesting

    If you skip over the assembly instruction that causes the exception in a debugger, everything works fine. So if anyone pulls this trick on you, just open the debugger and skip the instruction. :) That, or get a better browser.

    --
    using namespace slashdot;
    troll::post();
    1. Re:Pretty simple bug really by Nucleon500 · · Score: 1

      Actually, didn't older versions of Windows let you ignore GPFs, which usually didn't fix the problem but sometimes did?

  40. So.... by The+Bungi · · Score: 4, Insightful
    It's not a vulnerability. It's a bug. It's a stupid bug, but a bug nonetheless. I used to consistently crash Mozilla on some Hotmail pages. But I didn't submit it to /. as a great story to hysterical giggles from the peanut gallery.

    Slow news night, eh?

    1. Re:So.... by Anonymous Coward · · Score: 0

      Hmm, kinda weird, but I was trying to read the story and comments, and Phoenix crashed... no, really it did. I thought it was pretty ironic.

    2. Re:So.... by zook · · Score: 5, Insightful
      First: I agree.

      Second: It's simple. It's cute. It's the kind of bug that makes a dev go, "Doh!", and so it's not absurd to show some interest in it. It's also a fun game to try to pin down what the problem is.

      Third: Does it warrant a /. story? Have you seen half the stories that come through here? ;)

    3. Re:So.... by RoLi · · Score: 1
      I had some rare crashes with Mozilla 1.0, but after that I can't remember a crash.. (using 1.2 right now)

      Maybe you can post some html-code or link that crashes a halfway recent version of Mozilla?

      (Or were you just trolling?)

    4. Re:So.... by Realistic_Dragon · · Score: 0, Offtopic

      "I used to consistently crash Mozilla on some Hotmail pages."

      You must be lost - On Slashdot, Hotmail crashes Mozilla.

      --
      Beep beep.
    5. Re:So.... by Anonymous Coward · · Score: 0

      CowboyNeal's option should come back. It's all Jaqcues Chirac's fault.

    6. Re:So.... by Eudial · · Score: 2, Insightful
      It is a vounerability. DoS vounerability to be specific. By being able to totally screw up someones Outlook Express by appending '' into a html-mail. And since it is the newest mail, OE will render it every time he/she opens it.

      It can also be further exploited by javascript-based emailworms by adding a document.write("<INPUT TYPE 'Hastala visa baby'>"); after having spread itself to everyone on the contact-list.

      --
      GAAH! MY PRINTER IS ON FIRE!!! PUT IT OUT! PUT IT OUT!
    7. Re:So.... by KillerHamster · · Score: 1

      It's not a bug. It's a feature.

    8. Re:So.... by Master+Bait · · Score: 1
      This bug is not restricted to their browser, but the library used by all ms applications that render html. If you send an email as text to anyone using an ms email reader, or post to usenet as text and the message begins with , the html library will attempt to render it.

      --
      "Only in their dreams can men truly be free 'twas always thus, and always thus will be."
      --Tom Schulman
    9. Re:So.... by buckminster · · Score: 1

      Except that this 'bug' also affects outlook. For better or worse that's become the defacto standard email client in corporate america. So it seems like it wouldn't take much for someone to bring down a lot of mail clients by inserting this code into an HTML mail message. At that point people might start to see this as a serious vulnerability.

      No, it's not a slow news day, this problem could actually be quite serious. If for no other reason it could effectively cause a DOS for most corporate help desks.

    10. Re:So.... by Artemis · · Score: 1

      Have you ever used Outlook Express or do you just blindly bash it? If it OR Outlook crash while rendering/reading an e-mail message it will not render the message the next time Outlook/Express is started. This is not a vulnerability. Nor is it a "vounerability".

  41. Re:Phoenix by Anonymous Coward · · Score: 1, Interesting
    so the Mac coders at MS may be better coders...who knows.

    No, this is actually well known. IE for Mac got way ahead of IE for Windows, so the group coding the Mac version was dissolved a few years back to slow down development.

  42. Come on... by KoolDude · · Score: 0


    ...you can't blame IE for obeying the user's input. Just take a look at the source:

    <html>
    <form>
    <input type crash>
    </form>
    </html>

    you are basically asking it to crash at input and it obeys like a puppy. What's wrong with that ? Just becos Mozilla doesn't have this crash at input feature doesn't mean...

    me rushin 4 HTML101 labs... byeee

    --
    getSexySig(); /* returns sexy signature */
    1. Re:Come on... by isaace · · Score: 1

      That line isn't forcing it to crash. It's that the input type does not equal anything. If it said

      <input type xyz>

      it would still crash.

    2. Re:Come on... by Anonymous Coward · · Score: 0

      Ok try following...

      <html>
      <form>
      <input type do not crash>
      </form>
      </html>

      Still crashes. now it is a bug, right?

  43. Re:Microsoft...bleh. by Anonymous Coward · · Score: 0

    You must be new.. Welcome to Slashdot.. I hope you enjoy your stay. The restroom is in the back but please don't piss on the computer under the sink.

  44. Bill! Get it together, Bill! by fm6 · · Score: 2, Interesting
    The ease with which Microsoft software manages to generate invalid pointers has bothered me for a long time. But for the web brower to crash in the face of such a god damned simple HTML error is just plain scary. Here's the entire web page:
    <html>
    <form>
    <input type crash>
    </form>
    </html>
    I mean, does anybody in Redmond do any QA work at all? Or are they all too busy writing white papers, fighting lawsuits, and babbling about "freedom to innovate"?
    1. Re:Bill! Get it together, Bill! by Anonymous Coward · · Score: 0

      Thinking the QA people could catch this is insane. There is NO way you can test for EVERY scenario, and this seems like the last one you would test for. You must be a project manager or an end-user, same difference.

      Who is to say it wasn't caught by them? If you want your webpage to crash, why even put a page up there? This is nothing more than a null pointer exception comparing type to "HIDDEN" (you don't need "crash" in it, it was put there by a *nixhead for sensationalism). Typical fix, less than 5 minutes.

    2. Re:Bill! Get it together, Bill! by You're+All+Wrong · · Score: 1

      """
      babbling about "freedom to innovate"?
      """

      This latest crash is innovative, isn't it?

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    3. Re:Bill! Get it together, Bill! by fm6 · · Score: 1
      This latest crash is innovative, isn't it?
      Yeah, and crashing a comet into the planet speeds up evolution. ;)
      Your head of state is a corrupt weasel, I hope you're happy.
      disrespect for wartime leader detected. dispatching hit squad.
    4. Re:Bill! Get it together, Bill! by You're+All+Wrong · · Score: 1

      """
      Yeah, and crashing a comet into the planet speeds up evolution. ;)
      """

      Yup, good thing too. It needs a helping hand; the fitness functions are far too slack nowadays.

      """
      disrespect for wartime leader detected. dispatching hit squad.
      """

      In my country we have more enlightened electorate and politicians, and in fact now have both a female president and a female prime minister. We're also not at war. Hence "your", not "my". Sure, send the hit squads to get me anyway, I think it will be funny seeing US citizens trying to find this country! God help the neighbouring ones, though.

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    5. Re:Bill! Get it together, Bill! by fm6 · · Score: 1

      So you're in Finland, big deal. You issue traffic fines based on income, and people let the government prepare their tax returns. Crazy. Time you re-merged with Russia!

  45. Not just IE any application that uses its stuff by Anonymous Coward · · Score: 0

    Yahoo? MSN? How about embedding that code in the chat rooms :D or IM windows, and more.

    Lots of applications DEPEND on IE COM Components to do web stuff. ALways a good reason to update IE even if you dont use it, other apps do.

  46. Light-weight alright ;o) by maharg · · Score: 2, Interesting

    The error is invalid page fault in shlwapi.dll

    DLL Name: Shell Light-weight Utility
    Library Description: Contains utility functions for handling paths, urls, strings, registry entries and color settings

    Interesting that this dll can also 'handle' registry entries....

    In fact, the 5 lines of html can be reduced down to one:

    <input type>

    ..although placing this in the middle of a page doesn't always work:

    <html>
    <head>
    <title>foo</title>
    </head>
    <body>
    <h1>foo</h1>
    <input type>
    </body>
    </html>

    type seems to be the only attribute that has the desired effect

    --

    $ strings FTP.EXE | grep Copyright
    @(#) Copyright (c) 1983 The Regents of the University of California.
    1. Re:Light-weight alright ;o) by NoTildeQuestionMark · · Score: 1

      I instantly got to work making this a companion page to my JavaBomb (a JavaScript pop-up bomb that also works only in IE), and found that interestingly (to me), the bug does not work when couched between <BODY></BODY> tags, but that <TITLE></TITLE> tags are fine.

      So this works:

      <HTML>
      <HEAD>
      <TITLE>Crashing IE</TITLE>
      </HEAD>
      <FORM>
      <INPUT TYPE CRASH>
      </FORM>
      </HTML>

      But this one not so much:

      <HTML>
      <HEAD>
      <TITLE>Crashing IE</TITLE>
      </HEAD>
      <BODY>
      <FORM>
      <INPUT TYPE CRASH>
      </FORM>
      </BODY>
      </HTML>

      Which as far as I'm concerned is odd.

      ~

      --
      If you need me, I'll be hanging my computer from the
  47. Couldn't resist. by jkitchel · · Score: 5, Funny


    Who else couldn't resist from clicking on the link that would crash IE?

    1. Re:Couldn't resist. by DeathPenguin · · Score: 1

      It didn't bring down Opera 7.11TP5 for Linux :)

    2. Re:Couldn't resist. by Anonymous Coward · · Score: 0

      Yeah, and keep sending those error reports. I'll click it again just for fun. MWUHAHAHAHA.

    3. Re:Couldn't resist. by UnknownQ · · Score: 2, Funny
      Who else couldn't resist from clicking on the link that would crash IE?
      I couldn't, but then again I have Mozilla 1.3. I typed "BWAHAHAHAHAHA!" in the resulting text box.
      --
      Wherever you go, there you are!
    4. Re:Couldn't resist. by voidware · · Score: 1

      Yeah, I was kindof hoping it was slashdotted.

      brandon

    5. Re:Couldn't resist. by PovRayMan · · Score: 1

      I couldn't resist checking it either. I mean many people don't bother thinking about what they click and it could easily be disguised as something totally different.

      Oh a completely different note, check out some Free Porn you can download. Enjoy! ;-)

    6. Re:Couldn't resist. by Anonymous Coward · · Score: 0

      I crashed it 9 times just testing the stuff on thie forum.

  48. ME??? by Anonymous Coward · · Score: 0

    Microsoft ME stands for Miserable Edition. What did you expect?

    1. Re:ME??? by aarondyck · · Score: 0, Redundant

      What can I say? The only reason I have that PC is so that other members of my household won't be confused by Linux. There's only so much you can expect out of non-slashdot-type-people. Would it be possible to migrate everyone to Linux I would have tried already, but apparently the other members of my household are afraid to lose their blue screens and other miscellaneous features that MS was so kind to provide us with...Of course, it kind of pisses me off when they leave the blue screensaver on and tell me that I have to fix it...I've told them how to fix it--get Linux.

    2. Re:ME??? by Anonymous Coward · · Score: 0

      is so that other members of my household won't be confused by Linux. There's only so much you can expect out of non-slashdot-type-people.

      You big cool Linux guy you! Can I be as cool as you some day? I sure would like to be a big smart Linux person just like you. You big tough Penguin lover you.

    3. Re:ME??? by Anonymous Coward · · Score: 0

      The only reason I have that PC is so that other members of my household won't be confused by Linux.

      Doesn't that kind of tell you something about Linux?

    4. Re:ME??? by blixel · · Score: 1, Flamebait

      it kind of pisses me off when they leave the blue screensaver on and tell me that I have to fix it...I've told them how to fix it--get Linux.

      You're an elitist prick. You are the reason Linux is still so difficult to use. People like you are the reason other people don't want to use Linux. You think you are God, you're not. You're not even important. You are a sad, lonely, patheitc human who finds solace in dehumanizing others with your egotistical, arrogant, conceited attitude.

    5. Re:ME??? by bernywork · · Score: 0, Offtopic

      Mods.... Please mark parent as troll.

      --
      Curiosity was framed; ignorance killed the cat. -- Author unknown
    6. Re:ME??? by thynk · · Score: 2, Insightful

      I'm a big linux fan, I really am. I just don't really have the time to set it up properly if I'm working on something "non standard". After spending 2 days working to get Via Voice working on various linux distros I finally gave up and installed XP on the box. Total time till the project was done, less than one hour including install.

      What kind of makes me mad is when I request that our IT department install some software on my box at work. They leave it at the BSOD and try to blame me for it. Now that kind of thing stopped right away once my boss was backing me up. Now we have the only TWO home brewed PCs out of several thousand. Our IT department has admin access to them, but doesn't use it since we support them ourselves. Funny, hasn't crashed once since then.

      I think Linux has a very powerful user base, I think most people who run linux are a touch smarter than those who *can't* run linux or don't know any better than to run what their computer came with. I think *nix in general is far more powerful than winderz, but I think windows also has it's place in the market.

      Yes, this particular bug crashes IE in Windows. BFD. Opening Netscrape was iffy at best on a *nix box. The nice/scary thing about working where I do is we have 2 flavors of unix, dos 6.x to Windows 95, at least 3 distros of linux, a few NT boxes, several 2k boxes and even the odd OS/2 machine. Every OS has it's place and is useful in it's own right.

      Now, take a time out in the corner and meditate on these teachings of tolerance of other OSes.

      --

      Good judgment comes from experience, and a lot of that comes from bad judgment.
    7. Re:ME??? by Anonymous Coward · · Score: 0

      And while you're at it, mark Berny as a tool.

    8. Re:ME??? by Anonymous Coward · · Score: 0

      Mods - please mark parent up! Being one who has tried to help people learn linux by **TEACHING** them, its damn frustrating to read that kind of crap. The parent of this post is a well-deserved rant against the grandparent.

    9. Re:ME??? by NortWind · · Score: 1
      You big cool Linux guy you! Can I be as cool as you some day?

      Magic 8-ball says: "Outlook is bad"

    10. Re:ME??? by Anonymous Coward · · Score: 0
      Microsoft ME stands for Miserable Edition. What did you expect?

      No, it's a phrase from S&M. "Beat me, whip me, Windows ME!!!!!"

  49. hot air! by MavEtJu · · Score: 0

    Lots of hot air. Where is the time when, if you found a problem, just mailed the author saying "if you do this and this it will break." instead of writing a hundred line advisory?

    --
    bash$ :(){ :|:&};:
    1. Re:hot air! by hkmwbz · · Score: 1
      Well, it's a good way to get people's attention...

      That said, it seems that a lot of "vulnerabilities" are simply blown out of proportions. These security companies seem to be falling over themselves trying to get people's attention, whether it is warranted or not.

      Sadly, crashes in browsers are common. For MSIE. For Mozilla. For Opera. For Konqueror. Does this one really warrant a story on /.? I can swear I've seen similar silly crashes in all other "popular" browsers.

      --
      Clever signature text goes here.
  50. Re:Wait a minute.... by Anonymous Coward · · Score: 0

    I bet it's around 90%...

  51. Very big deal by fm6 · · Score: 5, Informative
    The IE HTML renderer is actually in a DLL that's shared by several application. And yes, they crash too. It's sort of interesting that that this DLL has no MacOS equivalent. Or perhaps there is an MacOS equivalent, but the usual low-level kludges are different on Mac and Windows.

    Why is this a big deal? Because the largest software company on the planet has no better development practices and safeguards than some half-literate garage hacker.

    1. Re:Very big deal by Troed · · Score: 0
      There's an older equally short exploit:


      <!-- IE-killer. All open IE-windows will be closed //-->
      <object id="test"
      data="#"
      width="0" height="0"
      type="text/x-scriptlet"
      VIEWASTEXT></object>

      ... which either crashes (v5) or closes down all open IE windows (v6) in Windows - but does not crash IE on Mac. It DOES however crash both Konqueror and Mozilla on the Mac - but not on Windows.

      I don't know what to make of it. I have that code running on the site in my sig just for fun - that's how I found out about the Mac-weirdness.

      Who's stealing code from who? ;)

    2. Re:Very big deal by Ed+Avis · · Score: 1

      You'd think they would run some kind of fuzz test to catch bugs like this. Paste together random strings of plausible-looking HTML (perhaps taken from real web pages) until one of them crashes the browser.

      --
      -- Ed Avis ed@membled.com
    3. Re:Very big deal by bsartist · · Score: 1

      It's sort of interesting that that this DLL has no MacOS equivalent.

      There was an HTML rendering widget in older versions of MacOS, but no one used it, because it sucked. It was basically only used by the help engine.

      Recently, however, Apple has begun beta testing a Cocoa wrapper around KHTML. They use it in their new Safari browser, and it will probably be finalized, documented, supported, and all that good stuff in 10.3.

      --
      Lost: Sig, white with black letters. No collar. Reward if found!
    4. Re:Very big deal by fm6 · · Score: 1

      When I said "No equivalent" I sort of implied "in the IE implementation". Microsoft would never use somebody else's renderer, even if it was standard for the platform they were using. They want all different implementations of IE to work the same. To fail to do so would undercut their campaign to get everybody to standardize on IE.

    5. Re:Very big deal by NineNine · · Score: 0

      You stupid clod. This is obviously debug code that was forgotten about and left in. It would NEVER be used in real life. It's not a big deal at all unless you like to make up your own HTML and run it in IE for fun (which was obviouisly done in this case).

    6. Re:Very big deal by bratmobile · · Score: 2, Funny

      Oh my god! Someone found! A BUG! In SOFTWARE! And it happens on TOTALLY INVALID HTML! How could Microsoft possibly make such a horrible, horrible mistake!!

      THIS NEVER HAPPENS ANYWHERE ELSE! Thank GOD the rest of the world is bug-free!

    7. Re:Very big deal by Anonymous Coward · · Score: 0

      So, one could assume that by using the phrase "half-literate garage hacker" you are including 95% of the Slashdot population? :)

    8. Re:Very big deal by Bishop923 · · Score: 1

      The Low level Mac OS X Equivalent to the iexplore dll is the apple port of kHTML that is being used in Safari. IIRC you can download the development kit and integrate an HTML renderer into any Cocoa App.

    9. Re:Very big deal by Anonymous Coward · · Score: 1, Interesting

      What about HTML-enabled messages in Outlook etc?
      What if somebody sends a SPAM with it? It is not virus, but anyway...

    10. Re:Very big deal by aePrime · · Score: 1

      You'd think they would run some kind of fuzz test to catch bugs like this. Paste together random strings of plausible-looking HTML (perhaps taken from real web pages) until one of them crashes the browser.

      I hope your joking, because this is just unfeasible, as there are an infinite number of these random strings, and probably very few which cause problems.

    11. Re:Very big deal by Anonymous Coward · · Score: 0
      It's not a big deal at all unless you like to make up your own HTML and run it in IE for fun


      "make up your own illegal HTML/whatever and run it in $app for fun" is what exploiting vulnerabilities is about.
    12. Re:Very big deal by ATMAvatar · · Score: 2

      It might not be such a big deal if IE wasn't embedded into Windows so deeply...

      We would probably hear much more about bugs/exploits in Mozilla if it gave root-level access to the machine :)

      --
      "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
    13. Re:Very big deal by Ed+Avis · · Score: 1

      There are an infinite number of random strings but also an infinite number that will trigger a particular bug (it's very rare to find a bug that manifests itself on one and one only input file... if you embedded that dodgy HTML form in a larger page it would still crash IE).

      Fuzz testing is a useful tool, of course it can't guarantee to catch all bugs, but it can often catch a worthwhile few. You just leave the machine running overnight and see what it comes up with. If ten million randomly created strings of junk HTML don't cause any problem, you can be reasonably confident that the code is of high quality, although of course you can't _prove_ that it is uncrashable this way.

      --
      -- Ed Avis ed@membled.com
    14. Re:Very big deal by RevAaron · · Score: 1

      Umm, the parent to which you replied is talking about an IE widget, not an HTML widget in general.

      OS X still has the HTML help. One can still embed it.

      The wrapper around the new-and-improved KHTML is called WebCore. Yes, Safari is based on it. And it works now, in 10.2, no need to wait for 10.3. The new OmniWeb uses WebCore for rendering and anyone could write an appthat uses it.

      --

      Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
    15. Re:Very big deal by RevAaron · · Score: 1

      IE for Mac was written from the ground up completely seperate from IE for Windows or Unix. I imagine there is some shared code, but it's not a port of the other IE.

      --

      Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
    16. Re:Very big deal by fm6 · · Score: 0

      Go read the HTML spec, and then lecture me. asshole.

    17. Re:Very big deal by fm6 · · Score: 1

      And you know this because...

    18. Re:Very big deal by WiseWeasel · · Score: 1

      It's called WebCore, based on kHTML. It is not a low level library accessed by several applications, but a open-sourced library that can be integrated into any app, and has recently been incorporated into iTunes, for the iTunes Music Store. Since each app runs its own copy of the library in their own memory space, it's less efficient, and more redundant, so one WebCore based app crashing will not affect others. This is contrary to the Windows IE HTML rendering DLL, which is used simultaneously by several apps, including Outlook and others, as I understand it. Given the choice, I'll pick the higher memory use and lower interdependency any day.

      --
      "I like systems, their application excepted", George Sand (French)
    19. Re:Very big deal by ibbey · · Score: 1

      Oh my god! Someone found! A BUG! In SOFTWARE! And it happens on TOTALLY INVALID HTML! How could Microsoft possibly make such a horrible, horrible mistake!!


      HTML should NEVER crash your browser. Error checking is a simple matter. The fact that a simple malformed tag can bring down the entire browser is a --very-- significant bug.

    20. Re:Very big deal by ibbey · · Score: 1

      This is obviously debug code that was forgotten about and left in.

      Even if this were true (it's not-- the "crash" is just an example, any word, or none at all, would work), that would not be a reasonable excuse. Standard coding practices say you delineate debugging code some how-- a comment, a constant, whatever-- so you can remove or disable it before you ship. Seeing as how this is a rather significant potential problem, if it were debugging code that wasn't disabled, I'd actually be even more harsh on MS. Bugs are a fact of life, though it takes a pretty incompetent programmer not to perform at least some level of error handling when dealing with user-input (as all HTML is). But not disabling critical debugging code rises above even that level of incompetence.

      It would NEVER be used in real life.

      Oh, I'm sure you're right. No script kiddie, slashdot troll, Goatse.cx fan, etc. would ever think of putting up a page like this maliciously.

    21. Re:Very big deal by Anonymous Coward · · Score: 0

      True. But then again, didn't mozilla pass the 1 million bug mark recently? Are we going to start posting stories on EVERY bug in it, too?

    22. Re:Very big deal by Rysc · · Score: 1

      You know that Mozilla "bugs" are pretty meaningless, right?

      --
      I want my Cowboyneal
    23. Re:Very big deal by Rysc · · Score: 1

      IE for Mac renders pages differently. Not just a little, REALLY differently. Until Mozilla came out IE5Mac was the most standards compliant browser around. If you were a web developer and tested your pages on many OSs/browsers you'd be familiar with this.

      --
      I want my Cowboyneal
    24. Re:Very big deal by fm6 · · Score: 1
      Until Mozilla came out IE5Mac was the most standards compliant browser around. If you were a web developer and tested your pages on many OSs/browsers you'd be familiar with this.
      I stand corrected.
    25. Re:Very big deal by Anonymous Coward · · Score: 0

      Ah, but there aren't an infinite number of strings of reasonable size... and a good random sampling of strings might not be a bad idea. I recently had a nasty bug in my own code that I spent two weeks trying to find. I finally wrote a random API caller and it uncovered the bug after 1 million (valid) calls.

    26. Re:Very big deal by bratmobile · · Score: 1

      I never said the browser SHOULD crash. Software should never, never, never, never, never, never, never, never, never, never, ever crash.

      But the fact is that this bug is totally unimportant. Sure, IE shouldn't crash. But this bug can only occur if you INTEND to hit the bug -- this is not normal HTML. And the crash does not expose any security hole (no buffer overruns, etc.), so it's just a crashing bug.

      So, Microsoft will fix it, and that's all. In general, IE has been FAR, FAR more tolerant of evil HTML than Netscrape ever was.

  52. Re:Microsoft...bleh. by theVicar · · Score: 2, Interesting

    It does surprise me... I mean, 'input type crash' ?? or is the input type significant or just for emphasis? It seems like what with 1-6, 8, and 9 of 9, plus all those eager-beaver interns and million typing monkeys at Microsoft this would have been caught earlier, unless the 'crash' thing was put there on purpose to intentionally cause a segfault or something so people could see what happens with all the activex controls etc. when IE does crash, and somebody forgot to remove it. Or, is Slashdot in permanent April Fool mode now? I hope so.

    --
    ---The Vicar---
  53. Hmm.. by chibiyoukai · · Score: 2, Interesting

    I haven't decided which is worse... The fact that such a silly bug exists, or the fact that it went undetected for six years.

  54. Crash by Hobobo · · Score: 2, Interesting

    A crash bug? Mozilla has none of those, right? Right? (seriously, if anything Microsoft should be proud that one pointless crash bug is such a big deal)

    1. Re:Crash by slaida1 · · Score: 1
      Because mozilla dev "team" has billions of cash back ing up it's developement, too. Yes that must be it.

      What I'm bitching about MS's fuckedness is their cash reserves and inability to USE them so that stupid bugs like this won't get into released products!

      --
      Preserve old classics: copy your collection onto all hard drives.
    2. Re:Crash by Anonymous Coward · · Score: 1, Informative

      Think before you bash.

      Ofcourse Mozilla has bugs. So has Opera, Konquerour and Safari, hell, maybe even Lynx have its flaws.

      The point is that about 95% of all Internet users browse with MSIE v5+, which makes this a pretty critical bug (and possible exploit)

      -smurk

    3. Re:Crash by Hobobo · · Score: 1

      You do realize that the "Mozilla" team is the Netscape team, which is owned by AOL?

  55. Ok ok, that's it, nothing more to see here... by Anonymous Coward · · Score: 0

    And now... Shall we continue to post all the bugs that crash Mozilla, Netscape or Galeon?
    Who first?

    1. Re:Ok ok, that's it, nothing more to see here... by Duckie01 · · Score: 2, Insightful

      And now... Shall we continue to post all the bugs that crash Mozilla, Netscape or Galeon?

      Sure. It'd be appreciated, too.

    2. Re:Ok ok, that's it, nothing more to see here... by Anonymous Coward · · Score: 0

      The difference is that if you find a bug in Mozilla and report it -- someone will fix it and we will have a better browser. Microsoft on the other hand will deny that there is a bug for as long as they can. Then, they will release a 10MB patch to fix the problem. And, nobody will install the patch. And, the next generation of their browser will have just as many stupid bugs as the previous one did. But, the marketing dept. will say that it's "better, faster and stronger" and millions of idiots will believe them. The more people that we can get off of using IE ... the better. I stopped using it 2 years ago and I'll never go back. Fuck Microsoft. Fuck them in their stupid asses.

  56. Re:Microsoft...bleh. by inaeldi · · Score: 2, Informative

    The "crash" part is just for looks. It would still crash with

  57. Needs to be tightened up by Anonymous Coward · · Score: 0

    Leave off the html and /html tags. Kills IE milliseconds faster.

    1. Re:Needs to be tightened up by Anonymous Coward · · Score: 0

      That's funny

  58. Re:Phoenix by bockman · · Score: 4, Informative
    Well, phoenix (0.5) crashes on my machine (Debian) in many ways, often downloading stuff. A couple of times, in not yet determined situations, it started to eat all memory, making the kernel to swap furiously until I killed phoenix threads.

    Nothing wrong with that, Phoenix being still an alpha product. But please do not compare it with mature products, even if they are from Microsoft.

    Also I don't understand why there are so many threads when nothing is going on (no download in progress and a single page shown).

    --
    Ciao

    ----

    FB

  59. Re:Wait a minute.... by petecarlson · · Score: 1

    I run MS Windows on my laptop and Linux on my web server and desktop. MS crap is good for some stuff and I am sure many Slashdot readers use it now and again.

  60. Wow by Anonymous Coward · · Score: 0

    It's amazing something like this went unnoticed for so long. I have no doubts this example will be cited for years to come when advocating the importance of open source. It makes me wonder what stress/syntax tests, or the lack thereof, MS's bug testers/quality assurance people did.

  61. Too bad for Mr. Gates by tankdilla · · Score: 1
    I'll bet he's not sleeping to well on his pile of money tonight. It would probably be really mean to set someone's homepage to that link, or set it to a local file with the code in it on one's own computer. They'd probably never be able to get on the internet again, unless they switch browsers.

    All I can say is Wow.....and LOL.

    --

    -Look lively. LOOK LIVELY!!! --Mr. Shmallow

    1. Re:Too bad for Mr. Gates by Anonymous Coward · · Score: 0

      I'll bet he's not sleeping to well on his pile of money tonight.

      That message sounded so stupid that for a moment I thought I was God. Thanks.

    2. Re:Too bad for Mr. Gates by Anonymous Coward · · Score: 0

      Or you can set someone's active desktop to a html file with the code. Boot up, then Bang, Crash, (error report).

      Of course, if they are never able to get on the Internet again they would never download another browser... they'd end up getting an AOL CD and moving from one evil empire to the other.

  62. not fixed yet... by Anonymous Coward · · Score: 0

    http://oca.microsoft.com/en/Response.asp?SID=96 and the clock is ticking

  63. test fix for IE by Anonymous Coward · · Score: 0

    According to a post on bugtraq: IE tries to compare the type of the input field to "HIDDEN", to see if it should be rendered. When there is no type string, a null-pointer is used. mshtml.dll calls shlwapi.dll#158 @ 0x636f0037 with a pointer to a static unicode string "HIDDEN" and a null-pointer.

  64. Worth Pointing Out, I Think by coloth · · Score: 5, Insightful

    I've crashed IE 6 several times with this HTML just fooling around, and each time, an exception is raised, a debug report generated, an optional offer is made to submit the report to the OS manufacturer to inform them of the problem, upon which immediate technical support is often given. After that action is complete, the OS remains stable, and the crash can be repeated ad nauseum, experimenting with different tags/debugger experiments/versions.

    That is in a consumer OS (XP Home) that costs less than $100, and has tens of thousands of commercial apps available in almost every language. (probably millions if you include shareware/freeware)

    Whether it's my mom or another engineer, I feel pretty good about telling them XP is a solid OS that can do what they need. (likewise with IE)

    Not many years ago, it would have seemed pretty petty to obsess about such a bug--and that's when it would've forced a reboot.

    I'm not shy about criticizing MS when appropriate, but to come from Windows for Workgroups to XP in 10 years is pretty impressive, especially for a company of its size.

    If it were me, I'd spend my time debating the Software Formerly Known As Palladium, and not lose the forest for the trees by mocking MS for this kind of item. I fart bugs bigger than this.

    --

    Machines take me by surprise with great frequency. -A. Turing

    1. Re:Worth Pointing Out, I Think by Anonymous Coward · · Score: 0

      I fart bugs bigger than this.

      Yuck!

    2. Re:Worth Pointing Out, I Think by Anonymous Coward · · Score: 0

      I fart bugs bigger than this

      You might want to stop shoving rotting meat up your ass.

    3. Re:Worth Pointing Out, I Think by Vidiot3k · · Score: 5, Funny

      You might want to get that checked out, I don't think it's healthy to fart bugs.

    4. Re:Worth Pointing Out, I Think by Realistic_Dragon · · Score: 1

      "I'm not shy about criticizing MS when appropriate, but to come from Windows for Workgroups to XP in 10 years is pretty impressive, especially for a company of its size."

      Not when free software has gone further, faster, and without obectionable and occasionally illegal business practices it isn't.

      --
      Beep beep.
    5. Re:Worth Pointing Out, I Think by cscx · · Score: 4, Informative

      What's most interesting about this is after the "crash/error/send error report" dialog pops up, I get a small message box that says "IE has encountered an error and will need to close. Click OK to do so." However, if you don't click OK you still have complete use of the browser. I am submitting this in IE after having clicked the "crash" link on the front page.

    6. Re:Worth Pointing Out, I Think by maraist · · Score: 1

      I'm not shy about criticizing MS when appropriate, but to come from Windows for Workgroups to XP in 10 years is pretty impressive, especially for a company of its size.

      I honestly can't tell if you're being sarchastic. 10 years to make an unstable piece of software less unstable and more bloated impresses you?

      Stable Enterprise-level product lines have been created from scratch in less than 5 years, and MS's inability to get past a horrific security/stability record with the largest software developer resources on the planet (hell, the largest "resources" on the planet) does little to impress me.

      That Bill Gates has finally announced that it's resources will be used to correct existing code is good (though probably just a show-boat). The issue is that they honestly value bloatware over quality.. Bloat means more to charge for. Unfortunately with high turnover rates, they don't have time to make stable software.... Other companies constantly build apon pre-existing bases, such that bugs can be found and corrected over time; new features are bug-prone, but the core becomes trust-worthy. This concept is decades old... Yet MS assumes that they can throw developers and "good software practices" at the problem and reinvent the wheel every 5 years or so.

      Moreoever, the only justification to reinvent the wheel is to drop compatibility with their crappy old software base.

      Look at Direct X, with it's 8,9,10 releases in less than 8 years. How can you trust that a video card driver (which now has operated at super-user levels for a while now) has had a chance to stableize? ATI has a horrible reputation for driver quality, but I don't blame them (much). They, like MS have bloat-ware concepts (put everything into their cards). But the number of features they provide hasn't grown too quickly.. But the platform for which they must constantly port, has.

      Moreoever, I can't comprehend how simple HTML tags can be allowed to crash the browser. Parsing is a trivial operation. Are there syntaxes in c that core-dump a compiler? For a run-time environment (VB-SCRIPT / JavaScript), sure, crashes might be evident; though this is a sign of a poorly constructed scripting language (perl crashes if you "goto" a label in another subroutine (via the "last" keyword)). But a browser can be defended by saying the definition of the scripting language is inferior.

      While this is a trivial bug, it just goes as proof of a design mentality that just isn't compatible with robust software.

      --
      -Michael
    7. Re:Worth Pointing Out, I Think by Politburo · · Score: 1

      Well that is certainly most interesting. Particularly because some people around here feel that "as long as you don't crash, you're ok", even if you render up a page that is goatse.cx when you clicked cnn.com.

    8. Re:Worth Pointing Out, I Think by Anonymous Coward · · Score: 0

      You fart bugs? You sick bastard.

    9. Re:Worth Pointing Out, I Think by Jeff+DeMaagd · · Score: 1

      Outlook Express crashes like this consistently with some forms of HTML mail (I think mostly spam), I think it uses the same renderer as IE. I don't have much control over what idiots send me via email. I think this exploit could be used to annoy a *LOT* of people, waste a lot of hours and still probably not cause much data loss.

      The problem is, it only crashes when retrieving mail, and it doesn't finish retrieving mail when it crashes. So starting it up again starts the cycle all over again, retrieve some email and crash again. It doesn't get anywhere.

      I have to pull up some other email program to complete the retrieve cycle so the emails are deleted from the server.

    10. Re:Worth Pointing Out, I Think by coloth · · Score: 1

      The issue is that they honestly value bloatware over quality

      I would say you're half right. To me what is more accurate is that they value REVENUE over quality.

      After all, MS is a business, not a religion.

      MS serves so many customers, they could publish 20 different builds of Word alone (academic, legal, engineering, literary, journalist, beginning user, etc...) And each one could be much smaller. Instead, they sell one build that includes all this, and it DOES erode the usability overall. However, from a cost-benefit standpoint, it's a much better business choice.

      It's like Democracy. Can't please everybody all the time.

      And, I just don't understand the "bloatware" concern in this era of consumer quarter-terabyte drives and 3 GHz processors. Granted, not everyone has this kind of hardware, but even on my 700MHz (500MHz SpeedStepped) 20GB laptop, I regularly run XP, IE, Word, and Excel with no problems. If the issue is with their interface design (to expose needed features), that's legitimate. But it's been a while since I've heard believable complaints about the size of an Office install.

      No pitchforks, please. I'm just trying to keep it real.

      --

      Machines take me by surprise with great frequency. -A. Turing

    11. Re:Worth Pointing Out, I Think by Anonymous Coward · · Score: 0
      That is in a consumer OS (XP Home) that costs less than $100...
      Less than $100? Quit trolling around, Mr. Ballmer!
    12. Re:Worth Pointing Out, I Think by maraist · · Score: 1

      I don't have a problem with them being a for-profit company.. And I don't mind that they have to cut corners here and there, and are ultimately trying to over-bundle things such that the average consumer has to pay more than they really want to. I am somewhat disturbed by the fact that consumers "have" to make these purchases due to peer compatibility. But most importantly (and relevant to this article) is that we are somewhat forced to use their software (at whatever price we can afford), and then are subject to a lack of quality control.. Part of corner-cutting is to get a product out the door before it's bug-list is even resolved (to say nothing of the shere number of undiscovered bugs).

      As for bloat-ware, I was focusing on the propensity of new code to be buggy. Thus the policy of adding every feature they can think of (so as to suit every type of customer) directly affects their ability to perform quality control - or more correctly, each new feature "should" increase the testing time by some amount.. Moreoever, the relationship between the amount of new features and the required time to test is non-linear (complexity grows somewhat exponentially).

      Thus, the marginal utility of each additional feature decreases. But the marginal price for each new feature remains the same.. But from the above, the marginal quality necessarily must decrease (unless, of course, the marginal time to release goes up; which it won't).

      win2k was called feature bloated; I've no doubt that win2k3 is the same. Each new sever-level feature is a new security risk, a new stability risk, and a potential unwanted cost.

      Finally, about your statement that modern machines have plenty of excess HD and CPU resources, remember the policy of wintel. Intel Makes a faster CPU, then MS adds bloatware which necessarily slows the system down (greater graphical load for the desktop, slower MFC, etc). The slowdown means that people/businesses are encouraged to repurchase new machines. Intel sells more CPU's, and get this, MS sells more windows licenses. So while whenever an application becomes bloated, it encourages a whole new purchase arena.

      Rest assured that 3GHZ is no safe harbor.. And while you as a consumer may not mind updating periodically to keep-up-with-the-joneses, businesses are less than thrilled to deprecate hardware/licenses.

      --
      -Michael
    13. Re:Worth Pointing Out, I Think by Anonymous Coward · · Score: 0

      I have that happen to me while I am just browsing the filesystem on my computer. IE needs to make sure that the ecxplorer has really crashed first.

    14. Re:Worth Pointing Out, I Think by Anonymous Coward · · Score: 0

      Not many years ago, it would have seemed pretty petty to obsess about such a bug--and that's when it would've forced a reboot.

      Running Windows 98 here, and I haven't had to reboot after trying that link.

    15. Re:Worth Pointing Out, I Think by coloth · · Score: 1

      get a product out the door before it's bug-list is even resolved

      It's a balance, right? When you're operating as a public company, you have a responsibility to the families holding your stock in their kids' college funds to get the product to market. And do it as soon as possible without any major negative ramifications. Microsoft Word, for instance, does not need the kind of stability that the avionics code in a 747 does. There is blowback from the strategy, but it's part of the business.

      I'm sure there are a lot of idealistic (and extremely talented) programmers who knock Microsoft's software, but couldn't compete with them in the marketplace, because shipping with a known (but relatively rare) bug is unacceptable to them.

      Nobody said MS was nice. Or that their software was perfect. But I think it's pretty darn good, considering it was created by a huge, monopolistic corporation.

      --

      Machines take me by surprise with great frequency. -A. Turing

    16. Re:Worth Pointing Out, I Think by coloth · · Score: 1

      Not when free software has gone further, faster, and without obectionable and occasionally illegal business practices it isn't.

      Nobody cares about the tens of thousands of shady deals or strongarm tactics employed by thousands of smaller corporations every day. People despise MS not because of their practices, but because it has succeeded.

      That doesn't excuse them, but if you condemn MS, I hope you're prepared to condemn a lot of western capitalism along with it.

      After all, cars emit poison gas, some more than others, but most people can still admire a nice one and sleep well at night.

      Millions of people have made hundreds of billions of dollars because of the platforms and "standards" that Microsoft has created. So it is not a giant vacuum cleaner.

      And, in my opinion, Microsoft's sins rank nowhere near those of Enron, for instance, where boundaries weren't just pushed, they were ignored or flaunted.

      Would MS be more palatable if it were lazy, lucky and sinful rather than hard-working, lucky and sinful? At least then we wouldn't be forced to wonder if it's our own lack of initiative that has allowed them to build their hegemony.

      --

      Machines take me by surprise with great frequency. -A. Turing

  65. Some quick notes by Lord+Bitman · · Score: 1

    - This crashes explorer as a whole, due to integration
    - To do it, use an [input] tag outside of the [body] tag, name the property "type" but don't define it, ie: [input type], not [input type=text].

    ta-da.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
    1. Re:Some quick notes by pod · · Score: 1
      - This crashes explorer as a whole, due to integration

      Mo it doesn't. At least not necessarily, not on Win2000, configuration depending. It crashes the current window of IE only, so even if you have other IE windows open, they're not affected.

      --
      "Hot lesbian witches! It's fucking genius!"
  66. oh, big deal by g4dget · · Score: 1, Insightful

    I don't particularly like Microsoft, but this is really not much of an "exploit". Mozilla crashes, Galeon crashes, Phoenix crashes, Safari crashes, and IE crashes. They crash due to particular snippets of JavaScript, DHTML, images, and plug-ins. As long as people keep writing end user applications in C/C++, they will crash. But they do so rarely enough that apparently most people aren't really bothered by it.

    1. Re:oh, big deal by arose · · Score: 1

      How many people are using Mozilla 0.96? How many IE 4.0?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  67. Re:Hah! I've got something that will crash IE also by Anonymous Coward · · Score: 5, Funny
    note: there is a bogus semicolon after the /td when I preview this post... it shouldn't be there, but I can't get rid of it.
    does IE crash when you use backspace?
  68. one line is enough by tmoerel · · Score: 1

    Just the single line: is enough to crash explorer. Keep in mind though that it only works if the input tag is not inside body tags. The code above does not crash the browser so if you build your HTML pages properly this bug should not affect you. Also, no chance of using it on forums or others.

    1. Re:one line is enough by Anonymous Coward · · Score: 0
      Also, no chance of using it on forums or others.
      You can use it to crash IE on every page that allows you to embed HTML into it. (You just need to do a <iframe src="site_which_contains_the_bad_html" /> - please note that site_which_contains_the_bad_html could be replaced with about:html_goes_here in IE versions that are a bit old (<IE6))
  69. Opera and Mozilla are not affected. by Taco+Cowboy · · Score: 5, Informative



    Tested with the Opera and Mozilla browsers, both on Windoze and Linux platforms, the exploit doesn't affect any of them.


    IE on the other hand, crashed.


    By the way, here is the entire "exploit code":


    <html>
    <form>
    <input type crash>
    </form>
    </html>







    --
    Muchas Gracias, Señor Edward Snowden !
    1. Re:Opera and Mozilla are not affected. by spectral · · Score: 5, Funny

      And the funny part is, you only need the input line. So therefore putting something like this on your page: <a href="about:<input type die>">Click here</a> to crash IE. will also work. Though it kind of gives it away how it works if you look at the status bar. Too bad /.'s filter won't let me post that link properly. Bleh. :)

    2. Re:Opera and Mozilla are not affected. by donkiemaster · · Score: 1

      you don't even need most of that, I tried it with a document that simply had "" (without the quotes of course) and that was enough to crash it for me

    3. Re:Opera and Mozilla are not affected. by questionlp · · Score: 3, Informative
      I believe the about:whatever has been disabled (with the key ones like about:blank and about:mozilla) by one of the patches in the IE6 "branch" as typing about:<input type foo> or using the HTML:
      <a href="about:<input type foo>">Click Here</a>
      just cases my installs of IE6 to come up with "Action canceled". Testing it under IE5.5 (with the latest patches) does indeed crash the browser.
    4. Re:Opera and Mozilla are not affected. by donkiemaster · · Score: 1

      oops, that was supposed to be "" (that will teach me to not preview)

    5. Re:Opera and Mozilla are not affected. by Guppy06 · · Score: 4, Funny

      <input type crash>

      IE is doing exactly what the tag is telling it to do. It's a feature, not a bug!

    6. Re:Opera and Mozilla are not affected. by spectral · · Score: 1

      Well that sucks. I used to like being able to whip up quick little pages in the location bar to form a link for something to download. Yes, annoying, but sometimes I have a link and IE is retarded and tries to view it, not save it. But I can't right click it and choose save as (for whatever reason. Stupid page not allowing it, etc.).

      I use phoenix now, but it IS somewhat useful. I think. Ok, prolly not.

    7. Re:Opera and Mozilla are not affected. by Steven+Blanchley · · Score: 1

      If you have JavaScript enabled, type something like javascript:document.write("<h1>this is an html page</h1>") in the location bar. That works for me on IE6 and Mozilla 1.4a.

    8. Re:Opera and Mozilla are not affected. by einhverfr · · Score: 1

      also crashes the browser. ;) One of the extremely common crash errors of expecting a string and finding a null ;)

      --

      LedgerSMB: Open source Accounting/ERP
    9. Re:Opera and Mozilla are not affected. by Anonymous Coward · · Score: 0

      *Looks at wet steaming pants*

      Yeah, that shits hot alright!

  70. Use a fresher Phoenix by peterwilm · · Score: 3, Insightful

    Unfortunately, 0.5 is very old and there are only nightly releases since then. Try the nightly build from March 20th. It haven't managed to crash it once in those weeks.

    1. Re:Use a fresher Phoenix by Rick+the+Red · · Score: 1

      What about memory leaks? In my experience 0.5 leaks like a sieve. Bugzilla shows outstanding memory leaks, so I didn't think they'd all been fixed yet. Do they fix bugs and not update Bugzilla?

      --
      If all this should have a reason, we would be the last to know.
    2. Re:Use a fresher Phoenix by peterwilm · · Score: 1

      I don't know about 0.5. The nightly build from March 20th seems to have still quite a few leaks. But not enough to affect the useability - in my opinion. I guess I will keep using this build still after 0.6 or 0.7 is out, because it just works. After having installed Java, Flash, Acrobat PDF-Viewer, RealPlayer and MPlayer there are just no open wishes any more :-).

    3. Re:Use a fresher Phoenix by Rick+the+Red · · Score: 1

      Well, the memory leaks are killing me. It's not so bad if I can only keep one window open, but so many web pages open a new window, even though I've told Phoenix to open new windows in tabs. Perhaps if that bug is fixed, the memory leaks won't be so bad. I'll give the March 20 build a try -- it's gotta be better than 0.5.

      --
      If all this should have a reason, we would be the last to know.
  71. this article makes FOSS community look like kids by Anonymous Coward · · Score: 0
    Yeah, there are pages that consistently crash IE. There are also pages that consistently crash Mozilla (hell, there are a lot of them), and Opera, and Konqueror. Even my ISP's home page brings Konqueror to a crawl (I fire up SSL-enabled Lynx for ISP config ;-).

    You know what, writing a web browser isn't easy. But not even Microsoft, with all its pro-Microsoft zealotry(!), has a forum which publishes a blow-by-blow list of every bug or vulnerability found in the 58 Free/Open Source browsers. "WE ARE BETAR THAN GAH-NU" is left to be dealt with in a childish way by the marketing dept: after all, the only competition they have (marketing wise) is.. well.. stuff like this forum.

  72. I spend too much time on Slashdot... by TrentC · · Score: 0, Troll

    I used to consistently crash Mozilla on some Hotmail pages.

    Is it me, or did the phrase "Hotmail isn't done until Mozilla won't run" run through anyone else's head when they read that?

    Maybe Slashdot is affecting me more than I thought. (If this post turns up twice, we'll know for sure...)

    Jay

    1. Re:I spend too much time on Slashdot... by damiam · · Score: 1

      No possible input stream should crash Mozilla (or any other browser). Not Hotmail, not , not 20 MB straight from /dev/random. It may not render correctly or even be usable on a given page, but it should never crash.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
  73. In other news by Anonymous Coward · · Score: 0

    World is round.

  74. It works. :) by blixel · · Score: 1

    Crashed mine. Version: 6.0.2800.1106.xpsp2.021108-1929

  75. What I really want to see... by weave · · Score: 4, Funny

    I want to see some simple HTML code that will crash a spammer's email harvesting web crawler. Now THAT would be "News.*that matters..."

    1. Re:What I really want to see... by Cybrr · · Score: 1

      You might like Wpoison.

      --
      Why did GEAR crush RDP?
    2. Re:What I really want to see... by Anonymous Coward · · Score: 0

      But you would have to be a spammer to find out if it crashes.

    3. Re:What I really want to see... by Anonymous Coward · · Score: 0

      Then ask Microsoft to develop an email harvesting web crawler.

  76. An infinite loop is not a bug in the application by Rares+Marian · · Score: 2, Interesting

    It's a bug in the document.

    What happens I guess is:

    1. You move the mouse outside the body to an image or off window.
    2. That blurs it.
    3. It wants focus, but the mouse is off the window.

    Somewhere javascript is point to self, so it runs focus, but the mouse is not on an object with any relation to javascript.

    This one may just be on the boundary between what is and what isn't.

    --
    The message on the other side of this sig is false.
  77. Write a worm.... by clambake · · Score: 2, Interesting

    Write a worm that sets everyone's home-page to this... so very evil.

  78. Re:Phoenix by mojowantshappy · · Score: 2, Insightful

    Yeah, I use the windows copy of phoenix and I have zero problems with it. In linux I just use Mozilla.

    --

    This page was generated by a Barrel of Circus Midgets, and that is the way I like it!!!

  79. Re:Damnit! by Deslack · · Score: 0
    It's not a serious vulnerability, but it sure is a very embarassing one :)
    I turn off ActiveX and Java on IE here and still, it manages to crash. This is serious.
    --
    .sigs are useless; it doesn't protect you from imposters.
  80. Garbage in, Garbage Out, was: Re:Hmm.. by Anonymous Coward · · Score: 0

    Christ, it went undetected for 6 years because it's bloody invalid code. Look at it, no webmaster in his/her right mind would ever markup anything like that. Head over to the W3C for info on how to use the form element http://www.w3.org/TR/html401/interact/forms.html.

    Better yet, run the markup through their validator http://validator.w3.org and see what the hell happens.

    1. Re:Garbage in, Garbage Out, was: Re:Hmm.. by Bedouin+X · · Score: 1

      Too bad the W3C spec says that if the type for an input element is not specified that it should be assumed to be a text input box.

      There are a few valid snippets using this exploit above that still crash IE.

      --
      Dissolve... Resolve... Evolve...
    2. Re:Garbage in, Garbage Out, was: Re:Hmm.. by chibiyoukai · · Score: 1

      Of course it was invalid code. However, it is good software testing practice to test your code using a variety of inputs to verify that all possible paths in the code are working correctly. This includes invalid input.

    3. Re:Garbage in, Garbage Out, was: Re:Hmm.. by duren686 · · Score: 1

      Testing for a variety of input cannot possibly catch all cases of all wrong input.

      --
      Y2K Compliant since the late 1890s
  81. I just found what to auto answer to all my spam... by ArcticCelt · · Score: 5, Interesting

    "This HTML also crash Outlook" Sweet, I just found what to auto answer to all my spam. Of course with a subject line that says: I am very interested to buy your products.

    --

    Yahh, hiii haaaaa! -Major Kong, from Dr. Strangelove
  82. Browser Filtering by mojowantshappy · · Score: 1

    This really isn't a bad way to break IE in the same way Microsoft broke Opera. I guess I will have to do that to the html docs I host on the web... whatever those are.

    --

    This page was generated by a Barrel of Circus Midgets, and that is the way I like it!!!

  83. Re:Microsoft...bleh. by Anonymous Coward · · Score: 0

    I mean, geez, you'd think that with a rep like MS that people would be expecting it!

    Maybe... but it sure is fun to e-mail these kinds of storys to all your MS loving friends!!

  84. Crashing Win9x by RayOfLight · · Score: 1

    Geee, thats almost as bad as the file:///C|/con/con thing that crashed the whole of Win9x.

  85. MSFT Mac Apps by green+pizza · · Score: 3, Informative

    Do you ever notice that when Microsoft makes a Mac version of a piss-poor Windows product that it tends to not suck [as much]?

    Somewhat. When it comes to Office, I prefer the Mac versions to those for Windows. Perhaps it's because MS had some extra time in bringing the Mac versions to market. (MS Mac Office 98 / MS Windows Office 97.... MS Mac Office 2001 / MS Windows Office 2000.... Office v.X for OS X doesn't really count as it's a hybrid of Office 2001 and Office XP). The look and feel seems easier to live with and the Entrouage email/calendar/pim app is a lot more sane than Outlook (though is lacking full Excange integration).

    MSN Messenger for the Mac is a pretty smooth little app... single file to deal with and none of the virus-like atributes of the Windows version.

    MS IE for Mac was pretty good back in the days of Netscape 4. But these days there are MUCH better choices for Mac users.

    Windows Media Player for the Mac (they need a better name for that app) works, but feels like quick and dirty port... I wouldn't be surprised if it wasn't done by the MS MBU (Macintosh Business Unit -- MS's Mac software team located in the Silicon Valley).

    1. Re:MSFT Mac Apps by nut · · Score: 0, Offtopic

      I don't know about that... I was working on a website recently at a new media company that used lots of Macs, and used IE as their main browser. I was doing a lot of javascript for them and I found a bunch of different ways to crash ie on mac with javascript.

      Our biggest stability problems were with IE on Mac.

      --
      Never trust a man in a blue trench coat, Never drive a car when you're dead
    2. Re:MSFT Mac Apps by Anonymous Coward · · Score: 0

      The company was still using OS 9 with IE4? That tells you something... that is nearly 6 years old... IE4 for the mac that is. At the time IE4 for the mac was the best knowen browset to man kind. You have to remember what your trying to do now just wasn't thought of back then, in somecase.

      And for now IE for OS X sucks major dog @$$ and MS just blames it on apple. Still doesn't explain why half the time java and java script kills IE or why it renderes blank pages, something that MS said they fixed back in the days of Mac OS X 10.0

    3. Re:MSFT Mac Apps by Ninja+Programmer · · Score: 4, Funny
      • Windows Media Player for the Mac (they need a better name for that app) works, but feels like quick and dirty port...
      No big surprise, it feels that way under Windows as well.
    4. Re:MSFT Mac Apps by wideBlueSkies · · Score: 1

      >> Windows Media Player for the Mac (they need a better name for that app) works, but feels like quick and dirty port...
      >>No big surprise, it feels that way under Windows as well.

      If I had points today, I'd mod the parent up as funny.

      Could someone please do this?

      --
      Huh?
    5. Re:MSFT Mac Apps by LafinJack · · Score: 1

      Somewhat. When it comes to Office, I prefer the Mac versions to those for Windows. Perhaps it's because MS had some extra time in bringing the Mac versions to market.

      More time? Not that I disagree, I much prefer the Mac versions of IE and Office too... but they've been working on the Windows version of Office for like, a decade. How much time do they need to make a decent Windows version?

      --
      we are building a religion
      a limited edition
      we are now accepting callers
      for these pendant key chains
    6. Re:MSFT Mac Apps by green+pizza · · Score: 1

      Good point. But keep in mind that Word and Excel were GUI apps for the Macintosh back in 1985. I outta dig up some old screenshots and/or find some old copies. As I recall, they looked a lot like the current versions, though with with far fewer features and much simpler & smaller toolbars.

    7. Re:MSFT Mac Apps by lithiumcloud · · Score: 1

      And someone else... and someone else...

      --
      This space intentionally left blank.
  86. Aren't you people missing something? by madmarcel · · Score: 2, Funny

    Whats wrong with you people?

    This is a *SPLENDID* way to keep internet exploder (l)users away from webpages.

    You don't want the average person to visit your website? smiple, insert 1 wee little line of code, et voila, bob's your uncle.

    Come to think of it...if /. were to use this code/bug/feature, would that keep the trolls away?
    (Hah! syeah right! Wishfull thinking ;^)

    <wonderful dream>
    It'll take 6 months before micro$oft fixes the problem, so that'll give the rest of us six months of troll-free slashdot happiness :P

    <reality>
    Having said that, I'm using Exploder on WinMe to submit this post - but mind you, it's the first time in 2 months I've been anywhere near windows - and yes, thats a real bug, it did crash - exploder only though...I figured windows would keel over with it. How eh...dissappointing ;)

    Ironic thoughts for the day:
    1) this IE bug WILL become a feature.
    <insert appropriate marketspeak here>
    2) This post will get rated 'Troll' :P

    1. Re:Aren't you people missing something? by Isofarro · · Score: 5, Informative
      This is a *SPLENDID* way to keep internet exploder (l)users away from webpages.


      Careful - we shouldn't stoop to invalid and non-standard HTML as a means of highlighting abusive and non-standards compliant browsers. So before implementing this, think about validity.

      Obviously, if we wrap this syntax up in a comment, it will be valid HTML. Now, considering Microsoft are stupid enough to implement conditional comments in Internet Explorer, we can wrap things up very nicely:
      <!--[if IE]><input type crash><![endif]-->
      There you go - something which is a valid comment, but MSIE decides to think its something else - like conditional markup.
    2. Re:Aren't you people missing something? by Hank+Powers · · Score: 1

      That only works when IE is in "quirks mode". It seems that if the page is valid XHTML, nothing special happens.

      So how to solve this? Insert the code so that it's right after <?xml version="1.0" encoding="iso-8859-1"?> but before DOCTYPE. That way the input field is read just before IE goes into the standards compliant mode.

      --
      hapo
    3. Re:Aren't you people missing something? by Phroggy · · Score: 1

      Thanks for making me aware of that interesting feature.

      This page passes W3C validation, and still crashes IE.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    4. Re:Aren't you people missing something? by 8string · · Score: 1

      It's pathetic that someone who posts this kind of drivel gets modded up. Unbelievable. What is wrong with you people?

      This is one of the stupidest stories I've ever seen on slashdot. I'm a linux/OS advocate, but that doesn't mean that I have to point fingers at MS for something this freaking petty. All finger pointing for this kind of minor bug does is make it clear just how many people hate MS, not how many people truely love OSS.

      Anyone who would intentionally penalize a user for using a browser they didn't like is just an ass. It's the true mark of a rank amateur with no professionalism at all.

      Go ahead, call me a troll.

    5. Re:Aren't you people missing something? by Steven+Blanchley · · Score: 1

      Microsoft intentionally makes some of their web sites work only in IE (MSN for instance, and now I can't seem to log in to Hotmail using Mozilla or Lynx). Why don't we try doing the reverse?

      Really, though, this is all to make a point to people: IE is a crappy browser that sucks. This is a truly ridiculous bug that shows MS's carelessness in designing it.

      The bug is not quite what I'd call "freaking petty," either. I use Mozilla with the more abusive features of JavaScript disabled, and I expect to be able to view any web site without it dealing any damage on my system or the programs running on it. But now anyone using Internet Explorer for Windows can have it crashed by 12 characters (25 on some versions?) of HTML. Freaking petty, indeed.

  87. IE Bug in five lines of html by physick · · Score: 1

    I read this note on "how to crash IE in five lines" and thought I would email it to a friend. So I made a little text file with the five lines and, perhaps foolishly, gave it the name of crash.html. I then wrote the email (in Netscape) and all was fine. Then I wanted to delete the file. Oops

    Simply selecting the file in the diretory and pulling up the right button menu crashed Windows Explorer and my laptop went to heaven. Just be sure I tried again this time debugging it with the Cancel option: still a dead laptop. I deleted it by deleting the whole diretory.

    I couldn't find any comments on the bug affecting anything other than IE. But it does.

    1. Re:IE Bug in five lines of html by owlstead · · Score: 1

      Yep, that should do it. You left your web content thingy on in explorer. This is the same as leaving preview pane on in OE or Outlook. Start up -> crash. Try to delete -> crash.

      Use a command prompt or use the classic view (recommended) to solve this problem. The current problem with Microsoft is the way it is integrating things in Windows. IE in OE and Explorer must be the single stupidest thing they did in times. Note that others are following suit though.

      What they _should_ have done was creating an HTML viewer that is not script, and forms enabled. Now with the modular xhtml modules, that should be fairly simple to do. Then they could just use the module with the limited functionality (read: the one that is less likely to crash).

      MB

    2. Re:IE Bug in five lines of html by thynk · · Score: 1

      Simply selecting the file in the diretory and pulling up the right button menu crashed Windows Explorer

      I think you'll find that saving it, and simply highlighting it will crash Windows Explorer, not even the need to right click. When I'm done playing around with it and sending to my friends with a warning I'll delete it from a command line.

      BTW - IE for Pocket PC 2002 doesn't crash with this bug.

      --

      Good judgment comes from experience, and a lot of that comes from bad judgment.
    3. Re:IE Bug in five lines of html by You're+All+Wrong · · Score: 1

      """
      BTW - IE for Pocket PC 2002 doesn't crash with this bug.
      """

      It fails to crash? Does that mean there's a bug in their implementation of the bug that makes it fail sometimes?

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
  88. NOoooooo by azzy · · Score: 0, Offtopic

    I got this story rejected on: 2003-04-24 21:46:57

    Would have been nice to give people more advance notice of this!

  89. no way by Anonymous Coward · · Score: 0

    I tried option , so if they can handle 32+ length, soon there will be no money at all.
    just wait a bit ;)

  90. Users look like kids on slashdot by Rares+Marian · · Score: 0, Flamebait

    Oooh, big roller coaster (browser).

    Of course it can break (crash).

    Slashdot: But the operator is drunk (it's a coding mistake in something independent of the browser).

    User: Nah, it's too huge, can't ride on it.

    The parser is broken in one small place in a very simple way that any coder should be able to catch.

    --
    The message on the other side of this sig is false.
    1. Re:Users look like kids on slashdot by Anonymous Coward · · Score: 2, Interesting
      Unix has had hundreds of buffer overflows in "small places" written "in a very simple way" that any coder "should be able to catch". It still took decades before an effort was even made to identify them, and we're still finding them now, despite the many man-years of auditing. Face it, no-one writes perfect code every time, not even Knuth, and most of us aren't even half way to his rigo(u)r.

      If you can identify all the bugs "that any coder should be able to catch" in every line of Linux kernel and GNU support code, so nothing ever goes wrong ever again on my system, I will personally pay you a full-time wage to do it. And so would Microsoft if you wished to do it for them. So, ready to convince us that you can debug the most complex consumer software?

  91. So? by ColaMan · · Score: 1

    This is kinda like the reason I don't moderate -In my profile - "I'd like to moderate, except IE goes beserk if there's more than 20 comments to moderate"

    Moderation boxes glitch and redraw all over the window when scrolling, or IE doesn't finish loading the page at all.

    Anyone else seen that? Maybe I should submit it to slashdot. "SLASHDOT CRASHES IE!!" ... yeah, that'll do.

    --

    You are in a twisty maze of processor lines, all alike.
    There is a lot of hype here.
    1. Re:So? by great+throwdini · · Score: 1
      Moderation boxes glitch and redraw all over the window when scrolling, or IE doesn't finish loading the page at all. Anyone else seen that?

      Yes. It's one reason why I stopped using MSIE 5.x on my Win98 machine. I've since stopped moderating, so I guess I can go back to MSIE.

      From what I recall from past discussion (this topic has been raised before many times in /. threads), MSIE is bound by certain versions of Windows to some rather confining limits when working with form elements. Too many form elements within a document, and the oddball behavior ("Web smear") shows its face.

      Never really encountered it outside of moderating lengthy topics on /. though, and only on Windows 98 - think it really only bites 95, 98, and ME (not XP or 2000+).

    2. Re:So? by BlacKat · · Score: 1

      No, I've had this problem in XP sadly... tho not all the time... but when it does occur it's a royal pain. :(

  92. Re:Damnit! by LordDragonstar · · Score: 1

    This is as serious as I am drunk. Very. However, I could see the necessity of the "exploit" to crash someone's browser through HTML since this seems to be intentionally allowed (from the exploit: ) which is perfectly good...oh wait, I only see that because intoxication has the better of me...good thing there's mozilla!

    --
    sig: There are two mistaakes in this sig.
  93. Parent: -1 Moron by Anonymous Coward · · Score: 0

    ..and my Konquerror didn't crash. Somehow I'm not suprised.

    Well duh... considering this is an IE bug...

  94. Re:Phoenix by Anonymous Coward · · Score: 0

    Do you also have a lot of threads show up when you run Mozilla? I believe this is a problem with the way top and the kernel identifiy threads, causing it show a bunch of extras. If you do have Mozilla running and it doesn't have this problem, my apologies.

    And I agree it should not be compared to IE.. There are messages to other developers in the options setting (unprofessional to say the least)... "XXXben we need at least a toggle here..."

    Hopefully 0.6 will be out soon, there are already tons of new features in the nightlies. Skin swapping without restarting, the completely redone preferences section, etc etc.

  95. Well, would you look at that? by ccbaxter · · Score: 1

    I'd better send Microsoft the automatic report they like so much...

    And again to be sure...

    And again....

    And again....

    --
    Dude, where's my Karma?
  96. Two points of significance for crashes. by jbn-o · · Score: 5, Informative
    I fail to see the significance.

    I see the significance in two ways right now:

    1. No matter what the input stream, the application should not respond by crashing.
    2. If the entire application crashes and the user had something valuable in another window, that data loss could be a big deal. As we become more dependant on web browsing ordinary users type more valuable data into browsers, often without thinking about the need for making backups by entering data in some other place and copying it into the browser.
    1. Re:Two points of significance for crashes. by evilviper · · Score: 5, Funny
      No matter what the input stream, the application should not respond by crashing.

      Man, do I wish someone would tell the Mozilla team that...
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    2. Re:Two points of significance for crashes. by Skuggan · · Score: 2, Insightful

      This is one of the bugs in MS Products that actually don't make a big difference.

      It's a usual bug. All browsers have them. This bug does *not* exist because MS is Evil. And MS probably will fix it, but I can't say they have to hurry. If someone inserts this text into a page to crash a browser, let him. It doesnt stop anyone to go to serious web sites.

      Get over it. Stop this useless bashing. I'm not in anyway pro MS, but this story has got to be a joke. And if I had paid for the Slashdot subscription I would have been able to see this breaking-story before many others... What has happened to this site?

      CowboyNeal - Help me!!! Come back. Plz

      --
      http://www.millnet.se/ GO/U d- s+:+ a C++ UL++++ P- L+++ E W+++ N+ w++ M-- PE+ t+ X++
    3. Re:Two points of significance for crashes. by Spoing · · Score: 4, Insightful
        1. No matter what the input stream, the application should not respond by crashing.

        Man, do I wish someone would tell the Mozilla team that...

      Got a current example?

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    4. Re:Two points of significance for crashes. by blibbleblobble · · Score: 4, Informative
      "Got a current example? [of mozilla crashing]"

      Yep. GNU/Linux/Windowmaker, visiting pages containing java, on a machine at best unfamiliar with the language.
      ps -a
      14472 java-vm [defunct]
      14475 java-vm
      14476 java-vm
      14479 java-vm
      ... etc
    5. Re:Two points of significance for crashes. by Zaiff+Urgulbunger · · Score: 1

      Agreed. I think a big issue could be Outlook being crashed since although most web sites are unlikely to include this code (might be a bit unpopular really), if someone were to spam a million addresses with this code, its likely to cause a lot more damage/lost data.

    6. Re:Two points of significance for crashes. by Zaiff+Urgulbunger · · Score: 3, Interesting

      Re potential for Outlook crashing, I'm not going to try this but if an outlook user receives an email containing this HTML then as soon as they view the email, Outlook crashes right?

      But the email would still be in their Inbox... so the next time they start outlook... oh just rememebered, Outlook Express (not sure about the full Office Outlook version) will not display an email after a crash.

      Worrying though!

    7. Re:Two points of significance for crashes. by FauxPasIII · · Score: 1, Funny

      > Man, do I wish someone would tell the Mozilla team that...

      I'm sure they'd be happy to give you your money back.

      --
      25% Funny, 25% Insightful, 25% Informative, 25% Troll
    8. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      If you want current examples...

      Go to bugzilla.mozill.org
      Click on Query Page
      Type 'crash' in the keyword field
      Push the search button

      Should be 683 or so bugs at this moment to look at.

    9. Re:Two points of significance for crashes. by BZ · · Score: 1

      This is why I highly recommend NOT running the Java plugin -- it's crashy.

    10. Re:Two points of significance for crashes. by SoupaFly · · Score: 1

      If the entire application crashes and the user had something valuable in another window, that data loss could be a big deal.

      It's just the current window, not the whole application... at least on my system w/ IE6sp1.

    11. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      Going to ZDNet always causes Mozilla to crash and burn for me. (Mozilla 1.3 on Slackware 9.0)

    12. Re:Two points of significance for crashes. by Reziac · · Score: 1

      That brings up another point: is there any such thing as a browser (or for that matter, a mail or news client) that autosaves or auto-backups your work?? (How many of us have written a long post or long email, only to have it eaten just before it gets sent?)

      Automatic save/backup was a standard feature in many apps from the early DOS era. Why is it so seldom seen in modern apps??

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    13. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      And if someone sends out a Melissa-type virus that modifies your registry to change your IE start page to to point to an URL containing this little snippet, would you still think that it "doesn't make a difference"?

    14. Re:Two points of significance for crashes. by autopr0n · · Score: 1
      --
      autopr0n is like, down and stuff.
    15. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      I'd settle for lost time.

    16. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      Done.

    17. Re:Two points of significance for crashes. by Superfarstucker · · Score: 1

      i wish somebody would tell opera that too.. whenever there is a plugin it can't handle or active x controls it goes tits up

    18. Re:Two points of significance for crashes. by Eskarel · · Score: 1
      It is actually as others have said a very big deal. Dealing with unexpected input is something which every even semi-knowledgable programmer should know about and be able to do, especially in a program which can take mulitple inputs at a given time(web browser). This is an example of either incompetence on behalf of the IE team or incredibly lazy programming.

      Regardless of which caused this particular issue it shows the general quality and security of the application. Buffer overrun errors are a fact of life with C, even the most experience programmers can miss one, as can be said of nearly all the aspects which cause serious flaws(short of poor design decisions like integrating something fundamentally insecure like a browser directly into the OS).

      If the IE programmers can't catch something like this, how can we expect them to catch the really serious stuff which novice programmers(the only kind who should still be getting these bugs) wouldn't even know about.

      Of course it's especially amusing since along with to a lesser extent Netscape, their tolerance of improper html has led to circumstances where this sort of thing can happen with relative frequency.

    19. Re:Two points of significance for crashes. by stinky+wizzleteats · · Score: 3, Insightful

      I must admit, there's something strangely fitting about a Microsoft apologist argument based on sheer arrogance.

      It's a usual bug. All browsers have them.

      An oddball javascript gyration that changes colors for the rest of the session is a usual bug. A fundamental HTML rendering flaw that can crash the entire Internet application suite for the world's most popular and profitable operating system is a big deal.

      This bug does *not* exist because MS is Evil

      Agreed. Never attribute to malice that which can be explained by incompetence.

      It doesnt stop anyone to go to serious web sites.

      It will if (as someone else has suggested) the next Melissa-type virus includes a payload to put the bad HTML on your computer and set it as your homepage.

      So much for security by indifference.

    20. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      How about zdnet.com or cnet.com. Both of them crash Mozilla within a few seconds.

    21. Re:Two points of significance for crashes. by evilviper · · Score: 1

      A wonderful attitude... I'm sure that will help free software take over the world.

      Internet Explorer is free as well.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    22. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      LOL!

    23. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0
      If the entire application crashes and the user had something valuable in another window, that data loss could be a big deal. As we become more dependant on web browsing ordinary users type more valuable data into browsers, often without thinking about the need for making backups by entering data in some other place and copying it into the browser.
      On IE 6.0 on Windows 2000, the particular window crashes, but not the entire application--other IE windows are fine.
    24. Re:Two points of significance for crashes. by rgmoore · · Score: 2, Informative

      I know that Galeon has an automatic "recover session" option. If the program crashes, the next time you start it you're given the option of re-opening it in its previous state. I'm not sure if it actually keeps track of what you had typed into forms, but at least it means that if you had twelve different, hard to reach pages open at once you can get back to where you were.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    25. Re:Two points of significance for crashes. by t · · Score: 1

      What I don't understand is why moz can't run plugins as separate processess, in their own memory space with IPC to shuffle data. Slow? Maybe, but one shouldn't prematurely optimize. And this method would also allow easier plugin development and testing by users.

    26. Re:Two points of significance for crashes. by gilroy · · Score: 2, Insightful
      Blockquoth the poster:

      Internet Explorer is free as well.

      Is it? Or do you have to shell out $200+ for an OS license?
    27. Re:Two points of significance for crashes. by moncyb · · Score: 1

      I upgraded to a nightly build (1.4a -- Gecko/20030303), and Mozilla doesn't crash there anymore. I have run into sites which make it crash, but the ZDNet bug appears to be fixed...

    28. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      Internet Explorer is free as well.

      Is it really? It doesn't run on any free operating systems, which means you have to pay to play. And look at the pricing history of Windows -- every time MS adds "free" features (IE being only one example), the price of the OS goes up accordingly.

      IE isn't free at all -- you've just been forced to pre-pay for it when you bought your OS. And if you don't use it, you've pissed that money away. There Ain't No Such Thing As A Free Lunch, especially from Microsoft.

    29. Re:Two points of significance for crashes. by juhaz · · Score: 1

      Seems to work all OK on 1.3 on w2k pro.

      Maybe you've got a broken flash plugin (I'm not saying Mozilla shouldn't handle those graciously as well, but it's not quite as bad as crashing from mere, even faulty, html)

    30. Re:Two points of significance for crashes. by usotsuki · · Score: 1

      You seem to forget, and this is an inherent problem with the name, that IE is *not* "jiyuu" free.

      Netscape/Mozilla *is*.

      I always say "free/open" or "jiyuu-free" to refer to the software I write, because that removes ambiguity. (jiyuu is Japanese for "freedom"; the equivalent of RMS's pet phrase is "jiyuu na sofuto", IIRC)

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    31. Re:Two points of significance for crashes. by evilviper · · Score: 1
      do you have to shell out $200+ for an OS license?

      Nope.

      Any version of Windows (3.11 should be cheap by now, as is 95, etc.)
      Mac OS
      Solaris
      Linux might be next...
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    32. Re:Two points of significance for crashes. by FauxPasIII · · Score: 4, Funny

      > Internet Explorer is free as well.

      Only in the same sense that the Sports Illustrated football phone is free.

      --
      25% Funny, 25% Insightful, 25% Informative, 25% Troll
    33. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      I wish my DHTML and Tables would work on Mozilla with out me pulling out my hair and spending 30 days writing a separate version..

      Works in IE.. Works in Conqueror.. Mozilla dies a firey death of mangled graphics and text.

    34. Re:Two points of significance for crashes. by jesser · · Score: 1

      Running Java in a separate process might also solve the problem where Mozilla hangs for 10 seconds when it loads the Java plugin. That would be a good thing and only people who count CPU cycles would consider it "slower". Bug 86634.

      --
      The shareholder is always right.
    35. Re:Two points of significance for crashes. by LPetrazickis · · Score: 2

      I know that Galeon has an automatic "recover session" option.

      Opera had it first.;) Unfortunately, it doesn't remember form contents either.

      --
      Is this a sigs-optional kind of place? 'Cause I am totally down with that if you know what I mean.
    36. Re:Two points of significance for crashes. by Pyrion · · Score: 1

      If the user is doing anything "valuable" with IE and it crashes, they should consider it a rite of passage.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    37. Re:Two points of significance for crashes. by bhtooefr · · Score: 0

      Parts of Mac OS are Free. The Darwin core is open source, the Safari browser is based on an open source core, which is based on KHTML and KJS. Tell me it's not Free. (And, all the stuff under the Darwin link is Free too!)

    38. Re:Two points of significance for crashes. by bhtooefr · · Score: 0

      lookOut 2000 will start back on the message. lookOut XP will ask if you want to start in "safe mode" (not displaying that message), or in normal mode (lookOut 2000 mode)

    39. Re:Two points of significance for crashes. by mah! · · Score: 1

      Internet Explorer is free as well.

      So is a kick in the mouth.
      I am sure it's easy to find someone willing to administer it.

      The point is: why would anyone want it?

    40. Re:Two points of significance for crashes. by shyster · · Score: 1
      It will if (as someone else has suggested) the next Melissa-type virus includes a payload to put the bad HTML on your computer and set it as your homepage.

      Right click IE, reset home page. Done. Easiest virus to clean ever. =)

    41. Re:Two points of significance for crashes. by Reziac · · Score: 1

      Oh, now that's nice. I'm sure we've all had the experience of FINALLY getting to the obnoxiously well-hidden support page on some corp site and losing it due to a crash! And if the page didn't fully load before going down, the URL may not make it into your History file.

      I'd think keeping track of forms input could be done -- sometimes what you've just Submitted in Netscape can still be found in a temp file, if you look before restarting NS. So at least what you tried to SEND could be saved (if not what you'd typed so far) -- I suppose it could be indexed akin to any cache element.

      [does quick search] I only come up with Galeon for Gnome (but Gnome and I don't like each other much). Do you know if it's available for Win32?

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    42. Re:Two points of significance for crashes. by stinky+wizzleteats · · Score: 1

      Right click IE, reset home page. Done. Easiest virus to clean ever. =)

      Good plan. Communicate that to 50000 users on a Monday morning using voicemail only (you daren't turn the Exchange servers on because of the virus).

    43. Re:Two points of significance for crashes. by shyster · · Score: 1
      Good plan. Communicate that to 50000 users on a Monday morning using voicemail only (you daren't turn the Exchange servers on because of the virus).

      Just distribute a registry patch via login script or GPO. Problem solved.

    44. Re:Two points of significance for crashes. by Anonymous Coward · · Score: 0

      try this to crash mozilla ( 1.3 )

      <html>
      <body>
      <button onMouseOver="this.style.color='black';" onMouseOut="this.style.color='white';" style="font-size: 11px;">click twice to crash</button>
      </body>
      </html>

    45. Re:Two points of significance for crashes. by stinky+wizzleteats · · Score: 1

      Just distribute a registry patch via login script or GPO. Problem solved.

      Ok. Of that 50000, 10000 never log out and don't know how to log back in. 32323 are already logged in by the time the registry patch is ready to be distributed, so now you have to tell them to log out and back in. 6732 of those interpret "logging out" as closing and restarting Outlook, and swamp your helpdesk with calls when the "patch doesn't work".

      The next day, 18046 users still have the problem, and 9763 will call the help desk to complain that the network keeps setting their home page back to the default you decided upon in the registry patch, and you spend an hour on the phone with some VP who cannot fathom why he can't set his home page to golfsportsgamblingsluts.com until the problem is resolved system wide. His complaints necessitate coordinating a multi-site nationwide effort to shut down every PC after hours so that they will get the update when the users turn them back on the next morning. You and 10 other people work until 4:00 doing it, and the next, day, 20 holdouts who work late hours and wouldn't let you touch their machine still aren't fixed. You turn off the registry patch after all of this, and then an oddball test lab Exchange server reinfects the entire network the next day.

      See, the problem here is that I am not only a Unix geek, but a former Novell CNE. That means that I know how a large computer network functions, from the users to the servers, and I know for a fact that this situation would not be as easy to fix as you would have all of us believe.

    46. Re:Two points of significance for crashes. by blibbleblobble · · Score: 1

      "This is why I highly recommend NOT running the Java plugin -- it's crashy."

      Now if only you could turn off Fireworks/Macromedia/Java/Flash support without a custom stylesheet, and more importantly, disable even attempting to look at the plugin, much less go searching for a player for it...

  97. <input type crash> will crash the browser... by eet23 · · Score: 2, Funny

    ... and will email it to all your friends as well.

  98. Get the Fix! by DarkHelmet · · Score: 3, Funny
    Windows Update:

    BugFix Q3823982

    This patch solves a vulnerability with Microsoft Internet Explorer Versions 4.0, 5.0, 5.5 and 6.0. A missing validation allowed snippits of code such as <form><input type cras.....

    -----

    This program has had a critical error and must be shut down...

    --
    /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
  99. Going on a Safari by sexysasian · · Score: 0

    Doesn't crash Safari. Wha' Wha'?!? Can't phase dis' shit!

  100. Not THAT serious... by KAMiKAZOW · · Score: 5, Informative

    I made some experiments and this bug is not that serious, if you use IE correctly.
    IE has a feature, Mozilla/Firebird and Opera sadly don't have: IE can run in multiple processes.
    If you open a new window by clicking IExplore.exe instead of pressing Ctrl-N, the new window runs in a seperate process. If you visit that crash page, only the one IE process crashes while the other processes stay unaffected (at least on NT based systems).

    OTOH if a page makes Mozilla crash, the whole app suite goes down. The process seperation with Firebird and Thunderbird is a step into the right direction, but different Firebird windows do still run in a single thread.
    I hope those kind of crashes send a message to all app developers (*cough*OpenOffice.org*cough*), to use multiple processes if possible (at least optional, because that would use more RAM).

    1. Re:Not THAT serious... by colinramsay · · Score: 1

      Re: Mozilla, the separation of the suite into Firebird & Thunderbird (or whatever they will be called) etc, is partly to solve this problem.

    2. Re:Not THAT serious... by glwtta · · Score: 1
      OTOH if a page makes Mozilla crash, the whole app suite goes down.

      You know what? I wouldn't know, haven't seen it crash once (of course maybe I'm just lucky).

      --
      sic transit gloria mundi
    3. Re:Not THAT serious... by ectospasm · · Score: 1

      ...different Firebird windows do still run in a single thread.

      Threads and processes are different. There could be multiple threads within the Firebird process (I don't know, I'm assuming that it is multi-threaded). If something crashes a thread, that thread dies, not necessarily the whole process.

      Just seemed to me you were mixing apples and oranges.

      --


      We are the music makers. We are the dreamers of the dreams.
    4. Re:Not THAT serious... by Soul-Burn666 · · Score: 1

      You are.
      My Mozilla crashes every now and then, but that's probably because i'm always using nightlies :)

      There was a time, about 2 months ago when it crashed every 5 mins, in all nightlies for about 2 weeks! Now it doesn't crash anymore :)

      --
      ^_^
    5. Re:Not THAT serious... by bobbyjack · · Score: 1

      ...this bug is not that serious, if you use IE correctly What? You mean there's a correct way to use IE?!? Why didn't you tell us earlier!? Oh, wait. You've just misunderstood the meaning of the word 'correct'... ;-)

    6. Re:Not THAT serious... by afantee · · Score: 1

      >> I made some experiments and this bug is not that serious, if you use IE correctly.

      Are you stupid or what? How can you blame users for not using it correctly when it can be crashed by such a simple HTML code? It's serious because IE is so widely used and the bug also impacts other MS programs like Outlook and FrontPage.

      >> IE has a feature, Mozilla/Firebird and Opera sadly don't have: IE can run in multiple processes. If you open a new window by clicking IExplore.exe instead of pressing Ctrl-N, the new window runs in a seperate process.

      You must be one of those MS trained idiots who know nothing but Windows. On a real OS like Mac OS X, Linux or any type of UNIX systems, all applications can be launched multiple times from a terminal and run in different processes.

      >> If you visit that crash page, only the one IE process crashes while the other processes stay unaffected (at least on NT based systems).

      You are probably too thick to realize how absurd your logic is, but it's as silly as suggesting that people should buy a hundred Windows PCs so that it's alright if one of them keeps crashing.

    7. Re:Not THAT serious... by SilentTristero · · Score: 1

      Actually on OSX most applications started by double-click (or open) just bring the current window to the front if an instance of that app is already running. It is moderately difficult to get more than one instance running. (The OS does this, not the app.)

      -- Tristero

    8. Re:Not THAT serious... by afantee · · Score: 1

      >> It is moderately difficult to get more than one instance running.

      That's because you don't know how to do it. All you have to do is to launch an application through the Terminal. For instance, you can start up as many Safari instances as you wish by typing "/Applications/Safari.app/Contents/MacOS/Safari " from a terminal window.

    9. Re:Not THAT serious... by SilentTristero · · Score: 1

      You're right of course. I meant moderately difficult for an average home or office Mac user -- power users can do pretty much anything on OSX.

      -- ST

  101. This is correct behavior by Christian+Schladetsc · · Score: 5, Funny

    // html_parser.cpp,v (C) 1990- Microsoft #include "html/parser.h" template void html_block(II F, II L) { for (; F != L; ++F) if (tag(*F)()) for (++F; F != L; ++F) if (tag(*F)::Type::val == Type::Crash) __asm int 3; } OK, they didnt use meta-programming C++ techniques, but there's code similiar to that in the IE source. This HTML rudely crashes IE: I didnt make that up. That's the actual contents of the html code that when processed by the HTML parser in IE crashes it. Its safe to look at here, because its not being processed by the parser - its being processed by the text renderer, which just draws text. Read it. Its not hard to understand, even if you've never seen HTML source before. The phrase "input type crash" demonstrates a clear intention, to, um, crash. It was included by the programmers for a number of very good reasons. I dont really care to list them all here. But this is clearly not a "bug". Actually, it shows good engineering practise. Microsoft rox0r. No, really, they do.

  102. Why wasn't this discovered earlier? by JustKidding · · Score: 2, Interesting

    I mean, hurds of people must have mistyped the input type tag at one point or another, how come we never heard of this before?

  103. Ode to Microsoft by nasim · · Score: 1

    your browser is crappy
    due to an error in shlwapi.

    when I browse the tag "input"
    Exploder goes kaput.

    --

    For great justice take off every sig.

    1. Re:Ode to Microsoft by Anonymous Coward · · Score: 0

      That's good! Here is verse two --

      I made a sig for Outlook
      including the tag "input"

      I sent it company-wide
      and now I'm trying to hide.

  104. You guys are all on crack by Old+Wolf · · Score: 1, Interesting

    Am I the only one who has noticed that this is obviously some debugging? They would have used such an instruction to test the crash recovery stuff, make sure data isn't corrupted during crashes, etc. etc. etc.

    It doesn't qualify as 'exploit' or 'bug'. It's not a security risk. It's not even a problem. IE crashes all the time anyway, you just re-start it (or you can even have it restart automatically) and you're back where you were (before clicking the link, presumably).

    Although this gives me an idea... what if you managed to set someone's default URL to this? Might take them a while to find out what's going on.

    1. Re:You guys are all on crack by Doppleganger · · Score: 1

      Except that the "crash" part isn't necessary... it can be set to any number of things and still cause the crash.

    2. Re:You guys are all on crack by Ensonik · · Score: 1

      That's not the point. You're probably right in saying that they left it there on purpose to test things. But by leaving it there, then it becomes a security risk therefore making it available for malicious use, just like you've suggested. That's what's wrong with it.

    3. Re:You guys are all on crack by Anonymous Coward · · Score: 0

      This is an exploit and a security risk.... if you don't believe it. Set your .sig file to be:

      <input type crash>

      And, email everyone in your company's Outlook mail directory. See what happens to productivity in your company when they all open the message.

    4. Re:You guys are all on crack by Zarf · · Score: 1

      Except that the "crash" part isn't necessary... it can be set to any number of things and still cause the crash.

      How much you wanna bet this is due to an improperly coded case statement? tee hee!

      Whee! I'm having so much fun with this! :) I'm off to try it out on Windows XP now with a whole mess of windows open called with the Ctrl+N command...

      --
      [signature]
    5. Re:You guys are all on crack by Old+Wolf · · Score: 1

      Actually, this word "crash" seems to be a red herring: all you need is . It crashes if there isn't a TYPE=something. Pretty awful, yes, but is it a security risk? I don't see how.

    6. Re:You guys are all on crack by tuxedobob · · Score: 1

      Actually, a crappy switch statement is the first thing I though of. Something like:

      switch(attribute)
      default:
      crash();
      }

      Frightening, really.

    7. Re:You guys are all on crack by Zarf · · Score: 1

      The "default: crash():" is the case statement inside the Switch block.

      --
      [signature]
    8. Re:You guys are all on crack by tuxedobob · · Score: 1

      Um. Yeah. I wasn't disagreeing with you. Though I did make two typos in that post. I'm too tired to do anything and not tired enough to go to bed. Bah.

    9. Re:You guys are all on crack by Zarf · · Score: 1

      *LOL* try reading some RFC's that'll put you to sleep. Better yet, any book on UML. But if you try and read anything about MS security or bugs then that'll give you nightmares!

      --
      [signature]
  105. Bugs, crashes by fm6 · · Score: 5, Insightful

    HTML clients are supposed to do skip over input they can't render. And in general, software should do something reasonable when it can't deal with input. Like deliver an error message. Crashing is always evidence of a bug, whether the data that caused it is buggy or not.

    1. Re:Bugs, crashes by Anonymous Coward · · Score: 0

      Correct me if I'm wrong, somebody, but to fix this properly, wouldn't you need to solve the halting problem? The browser would have to have an algorithm for determining whether a given state machine terminated correctly...

    2. Re:Bugs, crashes by craigeyb · · Score: 2, Funny

      Nah, it's a feature, man! It prevents IE users from seeing non-Microsoft-certified websites!

      --

      Social Contract? I don't remember signing any Social Contract!

    3. Re:Bugs, crashes by callipygian-showsyst · · Score: 1
      My SAFARI crashes ALL THE TIME. I don't waste the time of people on slashdot with that fact.

      In fact, there are web pages that will consistantly crash SAFARI. Why is nobody jumping up and down about this?

    4. Re:Bugs, crashes by Anonymous Coward · · Score: 0

      Because Safari is still advertised as a beta and, by default, one of the major buttons on its little toolbar is for bug reports. It's substantially easier to report the bug for this _beta_ than to submit it to /.

      Oh, and no, you don't waste the time of people on /., we waste our own time by being here.

    5. Re:Bugs, crashes by Cybrr · · Score: 1

      I don't think so. The halting problem seems to deal with chaotic simulations that don't have error catching.

      --
      Why did GEAR crush RDP?
    6. Re:Bugs, crashes by fm6 · · Score: 1

      It might have something to do with the fact that there are more IE users in Rhode Island then there are Safari users on the whole planet.

  106. Security Audits by aking137 · · Score: 2, Interesting

    If someone has left this around since 4.0, why haven't all these security audits Microsoft claim to be doing haven't found that out yet? Are we still to believe that they actually spent a whole month in early 2002 just rooting out security holes, when they didn't notice this? Or is someone going to try and say that they /did/ notice it and then deliberately didn't fix it, on the grounds that it's just a bug and maybe not technically a security hole? Come on, really...

    Andrew

    1. Re:Security Audits by Politburo · · Score: 1

      This isn't a security issue. This is a bug that crashes IE when a 5 year old writes HTML. They didn't deliberately not fix it, they just didn't know about it because no one had poked it this way.

  107. No wonder the new patch by thejackol · · Score: 1

    In other news, Microsoft has released a 10.2MB patch to get rid of a vulnerability in IE that malicious websites could make use of to crash the browser with 4 lines of code.

    1. Re:No wonder the new patch by Anonymous Coward · · Score: 0

      Except that the patched DLL is only 400k. Try again.

  108. just to make sure by InfoHighwayRoadkill · · Score: 1, Funny

    I tested it a couple of dozen times and sent the WinXP error reports of to Microsfot like any good windows user would...

    --
    another Roadkill on the Information Superhighway
  109. Re:An infinite loop is not a bug in the applicatio by jbn-o · · Score: 2, Insightful
    It's a bug in the document.

    No, if that does indeed crash an application it's a bug (and I'll assume, for the sake of argument, that the parent is correct even though other posters have stated they can't get Mozilla to crash from this). Applications should not respond to any input by crashing and applications should give the user a chance to lose data because someone on the net essentially (perhaps inadvertantly) instructed the application to crash.

    I appreciate the logic of the loop you're describing, but the proper response to that is not to crash or enter some state where a user's data can be lost.

  110. Wait a minute. by blanks · · Score: 5, Informative

    This makes it on to slashdot, but bugs like this Netscape exploit didn't?

    --
    I deleted my sig years ago.
    1. Re:Wait a minute. by Anonymous Coward · · Score: 0

      This is /. after all.... we are out to rip Microsoft a new asshole. Who cares about other exploits?

    2. Re:Wait a minute. by moncyb · · Score: 2, Funny

      Maybe because no one can read it? What does it say? It appears to use english words, but well...

    3. Re:Wait a minute. by k4m3 · · Score: 1

      It's an exploit, not a silly bug. There's a big difference between not cleaning some vars accessible via a scripting language, and crashing because one character is missing in the input stream. Furthemore, given the track record of IE regarding cross site scripting, that's not anymore a very interesting subject.

      I've tested the examples in the previous post and it doesn't seem to work...

  111. Who needs a few lines.. by Anonymous Coward · · Score: 2, Funny

    I'm running IE 5.x and it crashes constantly with any help from a few lines of html.

  112. yes, it is by Trepidity · · Score: 1

    If I currently have two windows open in Mozilla, and one of them has Javascript that goes into an infinite loop, the correct behavior is not for the entire program to crash, taking both windows down with it.

    1. Re:yes, it is by Rares+Marian · · Score: 1

      But this one is a reference to a window/button related function, not just some while true type deal.

      I'm just curious.

      --
      The message on the other side of this sig is false.
    2. Re:yes, it is by Reziac · · Score: 1

      Right on. That's why I like modularized programs. Getright is a good example. Say I have configuration, status, and half a dozen download windows going at once. If one of them crashes, it usually just affects that particular window, and all the rest keep right on running.

      With Netscape3, usually if one window gets confused, you can just close it, and whatever else is open at the time will not be affected.

      When I've had Mozilla crash, it's usually taken Windows right with it -- hard lockup, on a machine that had never even HAD a crash before. Seriously not-acceptable behaviour in my book.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  113. Re:Phoenix by snilloc · · Score: 2, Informative
    My experience with the Windows builds is that April 1 barfs a lot less than 0.5

    It still barfs, and it barfs in a slightly different color, but less often. Experiment with nightlies. When you find one that doesn't barf too often, go with it.

  114. MOD PARENT UP AS FUNNY by thynk · · Score: 2, Funny

    this is one of those times when I wish I had mod points. AH... maybe someday.

    --

    Good judgment comes from experience, and a lot of that comes from bad judgment.
  115. Re:An infinite loop is not a bug in the applicatio by Caktus · · Score: 1

    Evei if it is a bug in he document, the browser should never crash.

  116. Re:Phoenix by RoLi · · Score: 2, Flamebait
    But please do not compare it with mature products, even if they are from Microsoft.

    No offense, but many Alpha-products are perfectly comparable to ultra-mature Microsoft products like IE or MSOffice.

    Especially Phoenix/Firebird/Mozilla-Browser/whateveritscalled now which is very stable at least on my installation.

  117. BWAHAHA... by Anonymous Coward · · Score: 0

    ...HA!

    Seriously.

  118. 5.5 by Anonymous Coward · · Score: 0

    lol, explorer 5.5 under crossover office also crashes :-P

  119. Whoa! This is worst than I thought. by Anonymous Coward · · Score: 2, Interesting

    This does not just effect IE, it also appears to effect apps using the IE html rendering engine including Outlook Express and Frontpage.

    Try sending someone the crash code as an html e-mail. It crashed Outlook before even previewing. SHIT.

    I sincerely hope anti-virus software blocks this one soon.

    1. Re:Whoa! This is worst than I thought. by netsharc · · Score: 3, Insightful

      Is it really the responsibility of anti-virus makers to shield MS's bad programming with a it's-getting-bloatier-all-the-time syntax checker? I mean, it's good for Norton/McAfee that they can live out of MS's dumbness and user ignorance ("I run Norton, and no virus in the world, even the one that just came out today can affect me. A virus definition file, what's that?"), but heck, if you think Norton/McAfee should check everything that is to be sent to the browser, they'll pretty soon have a program as complex as the OS itself, just to check data. I think it's an OS maker's responsibility to build a whole OS, not let Norton/McAfee take care of the other half.

      --
      What time is it/will be over there? Check with my iPhone app!
    2. Re:Whoa! This is worst than I thought. by King+of+the+World · · Score: 1

      What I've come to learn is that responsibility only matters inside the industry, and most people don't care whose responsibility it is they just want it fixed. If a bit of software can stop IE from crashing then that's a good thing and most users will like it.

      It's funny that you use the virus checker example. It's the responsibility of virus makers not to make them and affect others machines, yet they do it anyway.

      Responsibility is about blame, and it's a human-level concept, outside of what's going to happen, and outside of nature.

      Virus checkers have gotten into the system stability software game a while ago, because so far as the user is concerned it's all related. I guess this will be tacked on that.

  120. This could turn into a new email worm by juniorkindergarten · · Score: 2, Interesting

    I just pasted the code into mozilla mail and emailed my outlook express 6 client and it caused it to crash. (Go figure)
    I haven't tried outlook 2000 yet. Anyone want to give it a shot?

    --
    "Every security scheme that is based on secrets eventually fails." - Steve Jobs
  121. Re:Microsoft...bleh. by mrjb · · Score: 2, Funny

    If you really want to prove a point, make sure its an html email then.

    --
    Visit http://ringbreak.dnd.utwente.nl/~mrjb/growingbettersoftware to download your free copy of the book
  122. Outlook Express affected by kh0ng · · Score: 2, Interesting
    Outlook Express uses the IE-Rendering Engine, so...

    One HTML-Message posted in a Newsgroup and containing the line "<input type>" (Shortest form of the exploit...12 bytes to crash IE) will kill all Outlook Expresses who try to read it (remember that OE _always_ displays the HTML-Version of the post), leaving the users puzzled and perhaps "insightful +5"...

    1. Re:Outlook Express affected by thechink · · Score: 1

      remember that OE _always_ displays the HTML-Version of the post

      There is an option in Outlook Express to read all email in plain text only. Which is the setting that I use all the time.

    2. Re:Outlook Express affected by thechink · · Score: 1

      Oops, correction you where referring to Newdgroups posts. You are right, they always display in HTML but then I never use OE for Newsgroups.

  123. Correction to the parent post. by jbn-o · · Score: 1

    I wrote:

    Applications should not respond to any input by crashing and applications should give the user a chance to lose data because someone on the net essentially (perhaps inadvertantly) instructed the application to crash.

    Obviously I mistyped and the above should read "...applications should not give the user a chance to lose data..."

  124. <input type="backdoor" /> by Anonymous Coward · · Score: 0

    I think this bug isn't dumb, it's the most
    clever backdoor ever created...

  125. I tried with Opera by Azahar · · Score: 2, Informative

    Opera 7.10 on Win 2k just gave a blank page leaving the other pages up and running no matter what identification I set it to.

    --
    Cuiusvis hominis est errare; nullius nisi insipientis in errore perseverare.
    1. Re:I tried with Opera by Old+Uncle+Bill · · Score: 3, Funny

      Those sneaky bastards must have QA'd that piece of code. How can MS really compete with that?

      --
      Yes, I am an agent of Satan, but my duties are largely ceremonial.
    2. Re:I tried with Opera by netsharc · · Score: 1

      Tested it with Opera 6.05 (on Win2K, this shouldn't matter though), and it crashed. I'm still using Opera 6, because Opera 7 seems to suffer the same bloat Winamp 3.0 has.. "ooo spiffy XML-modifiable GUI". Cool, but it's damn slow.

      --
      What time is it/will be over there? Check with my iPhone app!
    3. Re:I tried with Opera by netsharc · · Score: 1

      Cancel-post! Just tried it again, and this time Opera 6.05 didn't crash.. the earlier crash was probably caused by something else. Yay Opera!

      --
      What time is it/will be over there? Check with my iPhone app!
  126. Re:Phoenix by Alorelith · · Score: 2, Interesting

    I tried it in Netcaptor which is based on Internet Explorer--the page opened and the error message popped up, but Netcaptor kept on chugging. It's really a great browser. Offtopic, but when is Mozilla/Firebird going to incorporate something similar to Captorgroups. And don't even mention that multiple bookmarks on startup, that's not the same thing. Captorgroups are much more versatile.

  127. Re:Phoenix by Anonymous Coward · · Score: 0

    I just tried it with

    and that did it as well - who need 5 lines :-}

  128. should be up in arms. by http · · Score: 1
    i've now got a groovy plan to bugger my instructors. i will include this code in all my submitted assignments.
    they will have to contact me directly once they realize they can't mark the assignment if they can't read it, and i sent the email on time, so they can't give me zero...
    that's a (wild guess here) three day extension for most emailed assginments.
    Wa-hoo!

    yes, professor,i have a copy of the file i sent you...
    and there's a half-decent CYA, "i erased the email - my spool was getting full." this won't work if they're willing to switch email clients to something sensible that doesn't choke on the message

    To:
    From:
    Date:
    Subject:
    BEGIN
    this text will be treated as an attachment
    Microsoft...why bother?
    --
    If opportunity came disguised as temptation, one knock would be enough.
    3^2 * 67^1 * 977^1
    1. Re:should be up in arms. by Anonymous Coward · · Score: 0

      Let's hope they don't use IE. 'Cause if the do, the first thing they'll do when their browsers crash is look at the source. Or have someone more qualified look at it.

    2. Re:should be up in arms. by Anonymous Coward · · Score: 0
      i sent the email on time, so they can't give me zero...

      Want to bet? I would give you a zero and ask that you face disciplinary action.

      In my classes you could get a three day extention just by asking more than 24 hours before it was due. No excuse needed. Hack me and I'll fry your ass.

  129. IN SOVIET RUSSIA by Anonymous Coward · · Score: 0

    IE CrASHeS U!!!

  130. Re:Phoenix by pinny20 · · Score: 1

    The Mac Team at Microsoft seem to be a lot better at putting things together than the PC Team. Internet Explorer is actually quite nice to use on a Mac, as are things like Office.

  131. Re:Opera are not affected. by Anonymous Coward · · Score: 0

    Yep, Opera 7.03 on my Win95 system does not really need any HTML code to crash. It just casually does it from time to time to give me a break.

  132. Time to recognize a wider social significance. by jbn-o · · Score: 2, Insightful
    Of course any attempt to pass that as a security concern back then would have been laughed at. loudly.

    And undeservedly. People who could not see the potential for the web and understand that a critical application like a web browser must be made crash-proof should be corrected. Not by pointing and laughing, but by careful and patient explanation about how more people in everyday society depend on a well-functioning web browser that can handle any input (including input from potentially hostile webpage authors) without crashing (and thus losing what could be valuable data).

    I'm not sure what has fundamentally changed since then.

    What has changed since the days when people used Netscape's version 3 browser is an increase in the number of people who use web browsers for important work. Developers who don't take this concern seriously are not developers one should trust with important data.

  133. Outlook and Frontpage are also affected... by Uzull · · Score: 2, Insightful

    Just imagine : a spam mail using that code going to millions of IE / Outlook users... This would at least have one positive effect : Make the consumer aware that Yes, there are bugs and security issues in Windows and IE. You can no more read your email...

    1. Re:Outlook and Frontpage are also affected... by megabyte405 · · Score: 1

      wow, that's wicked. Very wicked. Let's hope teh 1337 do0ds aren't reading this. Here, though, is the one advantage to AOL: It doesn't render its email using IE (I don't think). Ironic, huh?

      --
      I recognize people by their sigs. Is that a bad thing?
    2. Re:Outlook and Frontpage are also affected... by Steven+Blanchley · · Score: 1

      Here, also, is one of many advantages to every mail reader other than OE.

  134. Outlook by Anonymous Coward · · Score: 0

    Shouldn't it be possible to crash outlook by sending a html-message with those strings in it, since outlook is using the IE render engine?

  135. Those who reject the future... by Omicron32 · · Score: 0

    I am now going to integrate this code onto all the websites I can change.... (all of 1).... and force people to use Mozilla.

  136. I set Opera to MSIE 5.0 and it didn't crash! by croftj · · Score: 1

    I think this story is just a troll!

    --
    -- Many men would appreciate a woman's mind more if they could fondle it
    1. Re:I set Opera to MSIE 5.0 and it didn't crash! by megabyte405 · · Score: 1

      I'm wondering if that comment was a troll, but I'll bite anyway. The MSIE 5.0 option in Opera just sets the referrer (So you can't be locked out of microsoft's site) to pretend it's IE 5

      --
      I recognize people by their sigs. Is that a bad thing?
    2. Re:I set Opera to MSIE 5.0 and it didn't crash! by franksp · · Score: 1

      I guarantee you that it really crashed, I tested it myself because I thought "they cant be *that* stupid", but it really crashes, my bad.

      ps. I have a win2000 and IE6 with the latest updates
      Francisco
  137. In related news......... by sjoel · · Score: 2, Funny

    in related news, the microsoft operating system is buggy and full of holes.

  138. dead by Anonymous Coward · · Score: 0

    killed ie6.0.2800.1106

  139. LOL by ktorn · · Score: 1

    LOL! :)

    Funny but interesting at the same time.
    Some one mod that one up.

  140. So what.. by destiney · · Score: 2, Informative


    Last time I checked I could still crash Mozilla with onSelect="select()" or an onFocus="select()" in a <textarea>.

    They all have bugs to some point. You're a fool if you think otherwise.

  141. Plain Old HTML by toriver · · Score: 1

    Because "Plain Old Text" on /. is just HTML without entities and with significant whitespace.

  142. Re:Damnit! by antoy · · Score: 1

    I turn off ActiveX and Java on IE here and still, it manages to crash. This is serious.

    What does Java or ActiveX got to do with it? It's an html parsing error.

  143. MS-loving friends? by Anonymous Coward · · Score: 0

    Doooooooood.... Time to get new friends! ...Ones that aren't clueless fuckwhizzles.

  144. confirmed: the crash happens by Anonymous Coward · · Score: 3, Informative

    Using IE6 on WinXP prof. with all SPs and updates installed.

    IE version: 6.0.2800.1106.xpsp2.021108-1929

    but I cannot see any obvious reason, WHY this happens. and WHY this only happens, when you put the mouse over the cell...

    actually a bit mysterious to me

    (Also checked: Mozilla 1.4a renders this page fine and has no problems with the mouse hovering over the cells. Again, mysterious, eeeeh...)

    1. Re:confirmed: the crash happens by MattCohn.com · · Score: 1

      No tag.

  145. HTML Crashes IE...And Windows XP Home by Anonymous Coward · · Score: 0

    Yes boys and girls it is true! I went to that page and it locked XP Home to the point of holding in the power button to turn it off so watch out!

  146. This is a feature, not a bug by Anonymous Coward · · Score: 0

    IE is for losers too stupid to use a real browser and Microsoft knows it

    1. Re:This is a feature, not a bug by rudy_wayne · · Score: 1

      Huh?

  147. hahahaha by 311Stylee · · Score: 1

    that's really funny.
    ie 5.00 collapsed instantly
    but then i read the code, "input type crash'?

    anyway, as it turns out the word doesn't have to be crash.. you can use any word you want, i used "killie" and got the same results...

  148. bu bu bu what? by sheemwaza · · Score: 1

    The secret command is crash? That's the kind of null pointer exploit command an idiot would put on his luggage!

  149. Why post IE bugs? by Britz · · Score: 1

    There are always people here on Slashdot that mock the rest of us for pointing at M$ errors and starting to jump up and down and scream like monkeys.

    Well, I get asked almost everyday by my friends why the hack I made the switch for my desktop computer from Windoze to Linux, when it is so complicated and frustrating sometimes.

    This is a good example why I did. I got stuck with a desktop machine that for some reason lost its TCP/IP ability after some time using it for no apparent reason. The only fix was to reboot it. And I got veeeery tired of reboots. In Linux I could have just mailed the creators of the drivers and have a high chance of resolving the problem if I include a core dump. In Windows I just kept switching every possible driver for my SCSI card, sound card, nic, mb ... Reboot, reboot, reboot, reboot. And this is just an example.

    Nowdays I use a laptop. Since I use it in my room mostly I have it plugged in and I can just put down the lid and send it to sleep (suspend to RAM). When I want to use it I just open the lid. I boot up in 3 seconds. I have Win98 preinstalled on the system and it still sits there (on less space) and I could maybe do one or two suspend to RAM after which it wouldn't wake up anymore and I had to ... guess what: REBOOT

    Disclaimer:
    OK, this is not a reboot bug, but one that can be verry annoying and could be dresolved by writing to the mozilla developer team and have it fixed in the next release in one or two month. I doubt if Microsoft will ever issue a fix.

  150. Only affects single instance of IE on XP by fudgefactor7 · · Score: 1

    Have one IE window open, then right-click on the page you want to go to (with the nasty lines of code), select open in new window, and only that new window will die.

    Not as big a deal as I had thought. I figured it would kill all instances of IE in use (and probably explorer as well.)

    1. Re:Only affects single instance of IE on XP by 0x12d3 · · Score: 1

      that's not strictly true; it depends on how you got those other windows. Each time you double click the IE icon, or use the "RUN" dialog a new instance is evoked. Different instances don't affect one another. If you Ctrl+N all windows crash together. This is always true, not just here (the moral of the story, is start a new browser instance for important work).

  151. Windows Media Dev. by Sophrosyne · · Score: 1

    The Windows Media player for mac was an unofficial port, it was actually done by like two people in their spare time within the Mac BU!!!
    talk about dedication! Perhaps with all the recent competition coming from Apple, Microsoft may begin to put more resources in Mac Development.

  152. Htm File Crashes Explorer Too! by bashbish · · Score: 1

    I saved the html file to disk so I could see the offending lines. It crashes Explorer file browser just by clicking on the file. I figure it is trying to render the little thumbnail view.

    Way to go backdoor Bill!

  153. OSS and the w3 falling behind - AGAIN! by IIRCAFAIKIANAL · · Score: 4, Funny

    I mean, IE implements the tags correctly and you all just noticed? Yet again we see that Microsoft IE is ahead of the game, implementing useful tags that the w3 hasn't even thought of yet.

    Why is it that Microsoft is saddled with the burden of creating useful standards? Isn't this supposed to be the job of the w3?

    I expect we'll have to wait a few years to see it in Moz and by then, microsoft will have implemented <input type explode into tiny pieces> or something even more spectacular.

    --
    Robots are everywhere, and they eat old people's medicine for fuel.
    1. Re:OSS and the w3 falling behind - AGAIN! by xutopia · · Score: 1

      actually what you think is a keyword here isn't. You can replace crash with any word you want.

      The word crash here was just used for fun. You are wrong in your assertion that this was done on purpose. Why would anyone put something in that crashes their software? And why does it only work if it is one of the first 5 tags in the html code?

    2. Re:OSS and the w3 falling behind - AGAIN! by Steven+Blanchley · · Score: 1

      It was a joke, you nimbus.

  154. XP either by Anonymous Coward · · Score: 0

    IE 6.0.2600 crashes on VMWare window at Windows XP... so funny hehe

  155. I got a fix... by miketang16 · · Score: 4, Informative

    http://www.w3c.org

    nuff said.

    --
    -------
    "In times of universal deceit, telling the truth becomes a revolutionary act."
    -- George Orwell
    1. Re:I got a fix... by juhaz · · Score: 1

      Wrong.

      Sure, it's not valid HTML, but it still shouldn't crash the browser. Sure, it's not first, and most certainly not last, time a browser will crash from html, be it valid or not, but this one is just so small and so stupid that it has amusement value over most others.

    2. Re:I got a fix... by Dirtside · · Score: 1

      I've got a better fix.

      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
  156. for all you headed to work/uni labs... by 0x12d3 · · Score: 1

    this works in the homepage field of your beloved browser:

    about:<input type>

    oddly enough if the '=' is included here an input box gets rendered (I haven't seen any other tag that is rendered for the homepage field. Hmm.....

  157. Re:An infinite loop is not a bug in the applicatio by Anonymous Coward · · Score: 0

    Mozilla 1.0.1 works just fine - displays an input box. Here is the page source:

    <html>
    <form>
    <input type crash>
    </form>
    </html>

  158. Re:Phoenix by spirality · · Score: 1

    The Mac Team at Microsoft seem to be a lot better at putting things together than the PC Team. Internet Explorer is actually quite nice to use on a Mac, as are things like Office.

    Compared to Safari? I don't think so, although I'll admit Office is about the best application in its class for Mac or any other platform. I've never tried Keynote though.

    Safari has never crashed on me, is scriptable via Apple Script, has Tabs, blocks popups, and generally looks much nicer. On the other hand IE crashes, does not block popups, does not have tabs, is ugly, and may be scripable (I don't know).

    The only thing I'll give IE, is that once in a while for certain sites I'll have to use it. For example my girlfriend must use it when registering for classes online. Safari doesn't cut it, although I believe Mozilla may for this task.

    -Craig.

  159. IE for the Mac is not IE for Windows by standards · · Score: 1

    I don't know who has noticed, but I'm quite sure that IE for the Mac is a completely different codebase than IE for Windows.

    In fact, IE for the Mac may be slow, but it seems to be much more standards-compliant than IE for Windows.

    I have never been able to recreate an IE for Windows bug in IE for the Mac.

    Then again, I agree with the parent post - there are lots of nice browsers for the Mac, and IE is my last choice.

    1. Re:IE for the Mac is not IE for Windows by edsel · · Score: 1

      The HTML rendering engine (code-name Tasman) in IE/Mac was the first browser to fully support CSS1 and DOM level 1.

      To see just how proud the IE/Mac team was of their accomplishment, try typing "about:Tasman" in the IE location bar. Looks a bit like the notorious Acid Box Test page, doesn't it?

  160. Careful with those emails! by Anonymous Coward · · Score: 5, Interesting

    I just sent a HTML email with this in to a friend who runs Outlook 2000. As soon as he got it, it crashed Outlook. Funny thing is every time he starts Outlook up it crashes again so he can't rmeove it. Disables his email program with one crafted email!

    1. Re:Careful with those emails! by HoaryCripple · · Score: 3, Funny

      Is he still your friend?

    2. Re:Careful with those emails! by netsharc · · Score: 4, Informative

      That sucks. :) Better find the Outlook.pst file (%HOME%\Application Data\Microsoft something something), which has all the data Outlook shows. Rename that file temporarily, start Outlook (it'll probably create a blank PST file), turn off the Preview Pane/AutoPreview, close Outlook and replace the new PST file with a copy of the original one. Hopefully you can then start Outlook with the Preview Pane turned off. Of course, this may not work when Outlook stores the Preview Pane settings inside the PST file itself. When that's the case, you can always go back to the previous method, but don't close Outlook and instead try to open the old PST file (Right click on "Outlook Today - [Personal Folders]" on the Folders List and choose "Open Outlook Data File...").

      Hey why am I bothering, you are AC and probably won't see this anyway.

      --
      What time is it/will be over there? Check with my iPhone app!
    3. Re:Careful with those emails! by Anonymous Coward · · Score: 0

      This is very insightful. The next virus writer to come up with an Outlook work like Klez or Melissa needs to include this code to take Outlook out for good.

    4. Re:Careful with those emails! by ArcticCelt · · Score: 1

      Well I run IE on Windows 2000 and because I was planning to send it as a reply to spammers, yesterday I tried it on myself to be sure it worked. It work great! ;) What is happening when you reopen outlook is that outlook position itself on the last opened email. The trick is just to click else were as fast as you can (you have almost one second) when you reopen outlook. Then you have many ways to delete the message without displaying it. Like turning of the html rendering etc... You can even click again on the message and as fast as you can press your delete key just before the message its displayed in html. It worked for me.

      --

      Yahh, hiii haaaaa! -Major Kong, from Dr. Strangelove
    5. Re:Careful with those emails! by PenguiN42 · · Score: 1

      That's odd.. When outlook Express crashes, and you start it up again, it specifically does *not* display the last email, in case that email caused the crash. It even displays a message to that effect.

      Does outlook express have this feature and outlook 2000 not? That kinda sucks, considering outlook 2000 is considered the more mature/higher level product.

      --
      The following sentence is true. The preceding sentence was false.
    6. Re:Careful with those emails! by Auckerman · · Score: 1

      I got one thing to say.
      "I Love You" Virus style outlook killer....
      That would ruin businesses everywhere.

      --

      Burn Hollywood Burn
    7. Re:Careful with those emails! by barfy · · Score: 2, Insightful

      um, a virus needs to be able to propogate. This would be as effective an epidemic as if SARS killed the carrier on contact.

      It is however a great way to piss off a friend or if someone had a good spam list, or a DOS of a company...

      But it makes a really bad virus.

    8. Re:Careful with those emails! by Anonymous Coward · · Score: 0

      Friends don't let friends use Outlook

    9. Re:Careful with those emails! by Anonymous Coward · · Score: 0

      Could you give some info on how you crafted the email?

    10. Re:Careful with those emails! by Anonymous Coward · · Score: 0


      From: Bill Gates
      Subject: Buy the new version of Windows now! This one has expired.
      Content-type: multipart/alternative; boundary="5D._.45_09._"

      This is a multi-part message in MIME format.

      --5D._.45_09._
      Content-Type: text/html;
      Content-Transfer-Encoding: quoted-printable

      <html>
      <head>
      <input type input>
      </head>

      --5D._.45_09._--

  161. Re:Hah! I've got something that will crash IE also by CCRancor · · Score: 2, Funny

    It's really not a bug - you're just moving your mouse too slow ;)

    --
    Open source is the art of letting other people write your bad code.
  162. It did not crash Lynx by drunk_as_in_beer · · Score: 5, Funny

    I repeat, it did not crash Lynx.

    --
    --Drunk as in Beer
    1. Re:It did not crash Lynx by bumby · · Score: 1

      netcat did not crash either:

      echo -e "GET /new.html\n\n"|nc vibrantlogic.com 80

      --
      Hey! That's my sig you're smoking there!
  163. I can't break my browser! by bob+dobalina · · Score: 1

    I can't get IE 5.2 for OS X to crash with this bug (nor safari). Watch, now someone will come along and tell me I'm not crashing my browser correctly.

    --

    B

    "I'm payin' taxes, but what am I buyin'?" -- James Brown

    1. Re:I can't break my browser! by Squidgee · · Score: 1

      Eh, doesn't work for me on OS X either; looks like (For once) the OS X IE is better than Windows' IE!

    2. Re:I can't break my browser! by megabyte405 · · Score: 1

      They have two entirely separate renderers and codebases, that's why you're immune.

      --
      I recognize people by their sigs. Is that a bad thing?
    3. Re:I can't break my browser! by Anonymous Coward · · Score: 0

      That's what you get for using a Mac. If you used a PC like everyone else... you could crash your browser too. ;)

  164. Jesus H fusking shit impaled-on-a-stick! by Pig+Hogger · · Score: 0, Offtopic

    Last week, I posted right here the fucking code that crashes it, and two assholes moderators moderated it into "reduntant".

  165. Please someone find a fatal flaw in NN4!! by Zaiff+Urgulbunger · · Score: 1

    Only yesterday I was wishing that someone would find some kind of fatal flaw in Netscape Navigator 4.x to force anyone using it to upgrade!

    I was having to make some beautifly crafted, standards compliant HTML/CSS work with the aformentioned thing.

    Quick poll: Does anyone here actually use NN4.x ? (apart from for testing which doesn't count)

    1. Re:Please someone find a fatal flaw in NN4!! by GuNgA-DiN · · Score: 1

      No. But, unfortunately, millions of users still do. I did some work for a client who kept complaining it didn't work right on their browser.... of course they were using NN4.x. It is their corporate standard and they had no plans to upgrade anytime soon. So, we ended up bringing out the damn browser sniffer and writing two sets of code. GRRRRRRRR.

    2. Re:Please someone find a fatal flaw in NN4!! by King+of+the+World · · Score: 1
      NN4 crashes for all manner of reasons, and it was crashing for me when I [LINK REL="STYLESHEET" HREF="FIlE THAT DOESN'T EXIST"].

      But then, as I said, NN4 crashes for all manner of reasons.

    3. Re:Please someone find a fatal flaw in NN4!! by You're+All+Wrong · · Score: 1

      Yes. I use w3m 50% of the time, Opera 50% of the time, but I can't get some of the plugins to work, so I occasionally have to pull up Nutscrape. Everything over 5 was either crashy as hell, bloaty as billy-boy-output, or crashy and bloaty. I kept having to go back to NN4.78, as it was the closest to workingness I could find. Bletch.

      YAW

      --
      Your head of state is a corrupt weasel, I hope you're happy.
  166. Did anyone notice? by FauWayGTi · · Score: 1

    I don't know if anyone else tooled around with the code, and I haven't read through all of the comments in this thread, but this exploit will crash IE with any invalid input type. You don't need to tell IE to "crash", you can tell it:

    <input type slashdot>

    if you want, and it will still crash.

  167. Crashing != bug by Anonymous+Brave+Guy · · Score: 1
    And in general, software should do something reasonable when it can't deal with input. Like deliver an error message. Crashing is always evidence of a bug, whether the data that caused it is buggy or not.

    No, it's not.

    I work on an industry-leading mathematical library. We rely, in a few places, on getting sensible input from our client apps. If they give us garbage, they have no guarantees about getting a sensible error back, or even about anything ever coming back.

    Before you say that this sucks, consider that if we did completely error-check all input to ensure that everything terminated properly with the current data set yada yada, our performance would almost certainly take an unacceptable hit in each of these cases, and in this business, performance kinda matters.

    In this case, crashing is not evidence of a bug, it's evidence of design priorities that don't match yours (but do match ours, and our customers').

    (Obviously I'm speaking only for myself and not my employer here...)

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:Crashing != bug by cculianu · · Score: 1
      I work on an industry-leading mathematical library. We rely, in a few places, on getting sensible input from our client apps. If they give us garbage, they have no guarantees about getting a sensible error back, or even about anything ever coming back.

      I must disagree with you there, Anonymous Brave Guy. There is a difference between your library and IE. One is a library while the other is a user application. Clients of a library are other programs (code) that link to the library and make calls to it. The application programmers that use your library can be given an exact spec on 'defined' and 'undefined' usage of each of the library's functions/methods. Each and every defined usage of the library is guaranteed to produce defined (non-crashing) results. Often undefined usage of the library is EXPECTED to crash the program immediately (this can help with developer testing and debugging.. having errors not crash a program but rather propagate out far beyond an errant call is often considered undesirable because it makes debugging more difficult.)

      However, full user appliations are a different story. They are expected to be ultra-robust and (ideally) crashproof. Especially mainstream 'consumer' apps like IE, which just about everyone that has ever used a computer has probably fired up once or twice in their life, if not every day.

      Computer programs need to be rock-solid. They need to be able to process input (valid or invalid) indefinitely until they are stopped by the user.

      For this reason this IE bug is unacceptable.

    2. Re:Crashing != bug by satch89450 · · Score: 4, Insightful
      I work on an industry-leading mathematical library. We rely, in a few places, on getting sensible input from our client apps. If they give us garbage, they have no guarantees about getting a sensible error back, or even about anything ever coming back.

      I'm sorry you don't mention the name of your company, because your company makes software that should be shunned. No software should respond in an astonishing way when fed valid data that is outside of the domain of the function -- it should do range-checking and set an appropriate error flag and return to the caller with something, even if that "something" is a NAN. Even when fed absolute junk, it should detect the junk and error out in a predictable manner.

      In particular, taking down the application (and perhaps the entire system it's running on) is not an option.

    3. Re:Crashing != bug by Reziac · · Score: 1

      Speaking from userland, I agree... if I do something stupid by accident, I don't want an "astonishing" result. If I input garbage, the program should at worst ignore me, and at best tell me how I was an idiot.

      "Stupid by accident" from a legit user is a real short hop from "malicious on purpose" by an unauthorized user. I don't want some unauthorized user generating "astonishing" results either!!

      So I agree with the first parent -- crashing means a bug is present, even if it's just failure to bounds-check. You don't need to idiot-proof it, you just need to make sure it doesn't behave ungracefully when assaulted by an idiot.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    4. Re:Crashing != bug by Anonymous Coward · · Score: 0

      I bet you love Java, Exception Ho.

      --
      Wank it at SmoothPorn.

    5. Re:Crashing != bug by Malc · · Score: 2, Insightful

      Rubbish. A library has to be bullet-proof too. For example, look at the bugs in the C library for malformed input - the worst ones result in buffer-overflows that result in remote exploits.

    6. Re:Crashing != bug by jbolden · · Score: 1

      He writes a library not software.
      Try feeding invalid data to most of the C standard library and you will often get creashes.

    7. Re:Crashing != bug by NickFitz · · Score: 2, Interesting
      You don't need to idiot-proof it, you just need to make sure it doesn't behave ungracefully when assaulted by an idiot.

      It's impossible to do that. Turing demonstrated that it is not possible to determine whether any given algorithm will execute to completion for all possible inputs. As the library in question is a mathematical one, it will undoubtedly contain algorithms which will not complete for some input or inputs, and all the bounds-checking in the world cannot guarantee security from input which will cause an infinite execution time. If it was possible, it would be a solution to the Turing machine halting problem, and such a thing cannot be, by definition.

      --
      Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
    8. Re:Crashing != bug by NickFitz · · Score: 2, Funny
      He writes a library not software.

      What, like a mediaeval monk? ;-)

      --
      Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
    9. Re:Crashing != bug by e-Motion · · Score: 1

      Rubbish. A library has to be bullet-proof too. For example, look at the bugs in the C library for malformed input - the worst ones result in buffer-overflows that result in remote exploits.

      The post to which you replied is exactly right. Libraries are very different from applications because developers can be expected to deal with the erroneous conditions that a library cannot handle, whereas (in an ideal world) users should not be expected to work around an application's flaws. If the application encounters a scenario that it cannot handle, it is expected to deal with it gracefully. A library can simply document that it can't handle certain conditions and then expect the application developer to avoid those conditions before using functionality contained in the library.

      The C library doesn't inherently contain bugs, but I suppose a particular implementation could have bugs. What you are talking about could most likely be classified as design flaws. For instance, gets() is inherently unsafe, and strncpy() has questionable behavior on certain input. These problems are not bugs, though, because the functions behave exactly as specified. As developers, we are expected to use the functions contained in the C library correctly.

      If you are not happy with the C library, then wrap it. That way, you can create a library that meets your expectations without imposing such error checking on other developers who don't need it. Personally, I like it the way it is.

    10. Re:Crashing != bug by Anonymous+Brave+Guy · · Score: 1
      I must disagree with you there, Anonymous Brave Guy. There is a difference between your library and IE. One is a library while the other is a user application. Clients of a library are other programs (code) that link to the library and make calls to it. The application programmers that use your library can be given an exact spec on 'defined' and 'undefined' usage of each of the library's functions/methods.

      I don't think we're disagreeing at all. Your point is exactly the same as mine: the parent post to which I replied claimed that in general, crashing software always means a bug, yet under circumstances such as those you describe here, this may not the case.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    11. Re:Crashing != bug by e-Motion · · Score: 1

      No software should respond in an astonishing way when fed valid data that is outside of the domain of the function...

      If a library function is fully documented and states that data within that range will not be handled by the function, then it can do whatever it likes if you pass it data within the invalid range. At that point, all bets are off, and it's your fault, not the function's fault. Libraries do not have to be idiot-proof, they just have to be fully documented and well-designed.

      Developers are not idiots. Well, at least I know I'm not an idiot. I can't speak for everyone.

    12. Re:Crashing != bug by Anonymous Coward · · Score: 0

      The never-ending chore of error-handling... While I have to agree with Anonymous Brave Guy on the design decision argument, I disagree on the general applicability of that argument. A program with the purpose of processing data which is 99.9% from untrusted sources should under no circumstances crash due to malformed data. A design decision which deviates from that absolute expectation is simply wrong. It should also be noted that even the "infinite" execution time problem can be handled. Many programs do this: When the execution time of a function exceeds a certain threshold, the user is given the option to end it. This kind of intervention requires that the algorithm is able to handle stop requests gracefully. Coding it that way can be a really frustrating task but is not impossible.

    13. Re:Crashing != bug by Anonymous+Brave+Guy · · Score: 1
      A library can simply document that it can't handle certain conditions and then expect the application developer to avoid those conditions before using functionality contained in the library.

      Thank you. This was exactly my point.

      In fact, this is often the only reasonable course of action, since the performance penalties associated with validating all input to the library at source can be prohibitive. Checking for a NULL pointer is easy. Checking the linked list you've given us isn't circular takes time. Checking the graph you've given us really is a DAG takes a lot of time. As someone else pointed out in this thread, checking some inputs would probably require solution of the Halting Problem.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    14. Re:Crashing != bug by Anonymous+Brave+Guy · · Score: 2, Insightful
      No software should respond in an astonishing way when fed valid data that is outside of the domain of the function -- it should do range-checking and set an appropriate error flag and return to the caller with something, even if that "something" is a NAN.

      Please tell me you're not just talking about things like forgetting to check before dividing by zero or SQRTing a negative number! If you are, then you are totally misunderstanding this conversation. We're in a different league here.

      Even when fed absolute junk, it should detect the junk and error out in a predictable manner.

      Unfortunately, you've spent so long checking that your algorithm will work correctly and terminate (assuming such checks are even possible) that no-one else will ever use your code because the alternatives are several orders of magnitude faster, which is the dominant requirement for the type of software we provide.

      Any library can get bad input. You can pass me a pointer to your data structure and claim it's valid, but actually give me an address outside of memory that I'm allowed to access so I segfault when I follow it. It is not possible to write a 100% bulletproof library in this situation.

      You have to trust your calling code to do its job, and you have to be clear about what input you accept with defined results so those writing the calling code can do their job. There is no other option.

      The only remaining question is how broad you choose to make the set of valid inputs. This is simply a trade-off between safety and performance, and in this particular industry, standard practice is to trust your caller and go for performance. You're necessarily relying on them to give you good input anyway, so further checks just slow you down without any real safety benefit.

      In particular, taking down the application (and perhaps the entire system it's running on) is not an option.

      Actually, taking down the whole application and providing diagnostics is one of the better options, since it makes it clear during testing that there is a bug, which in turn implies that our client application has a logic error somewhere in it.

      If my library doing something can take down your whole system, your OS is broken, of course.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    15. Re:Crashing != bug by Anonymous Coward · · Score: 0

      If the valid input range can be defined precisely, the library can check that input is in the allowed range. It's called programming by contract. These checks take time, so they are not always desired. But is that applicable to libraries which process complex data? If application developers were supposed to sanitize the html code before passing it to the library, then what would be the point of using the library? Microsoft is about to unleash "trusted" computing, a concept which is based on the assumption that the system should not trust all applications. That kind of system simply can't afford to omit sanity checks.

    16. Re:Crashing != bug by Anonymous+Brave+Guy · · Score: 1
      A program with the purpose of processing data which is 99.9% from untrusted sources should under no circumstances crash due to malformed data.

      That may well be a sensible design decision. However, the "untrusted sources" part is significant. A lot of software is written in an environment where it is reasonable to trust your sources, and in those cases, it may be undesirable to introduce slow error-handling code. The post to which I first objected claimed that in general it was true that any software that could crash had a bug, and in this environment that is simply not the case.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    17. Re:Crashing != bug by Anonymous+Brave+Guy · · Score: 1
      Speaking from userland, I agree...

      Not all software is written for end-users, or taking input from untrustworthy sources.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    18. Re:Crashing != bug by satch89450 · · Score: 1
      Try feeding invalid data to most of the C standard library and you will often get creashes.

      Feed a null pointer to a properly-written C library and you get a diagnostic, not a crash. Feed a pointer to a string that is not zero-terminated and you will get astonishing effects, but that's from poor language design, not poor implementation. For example many of the str* functions are hard to do with crash protection, although there are techniques to deal with the problem without costing too much performance.

      I've worked on libraries, and it's possible to deal with issues without compromising performance and capability. It does add a small amount of bloat, but in many cases it's worth it.

      It's been a long time since memory was measured in cents per bit.

    19. Re:Crashing != bug by satch89450 · · Score: 1
      Developers are not idiots.

      Then where do all the buffer overruns come from? I'm not saying that developers are idiots, but every developer makes mistakes. Bugs are usually rooted in opportunities for error, so whatever your library can do to help trace brain farts is time and effort well spent.

      I guess I look at maintenance and integration issues in development, more than some people do, because of my background in DVT and QA.

    20. Re:Crashing != bug by e-Motion · · Score: 1

      Then where do all the buffer overruns come from? I'm not saying that developers are idiots, but every developer makes mistakes. Bugs are usually rooted in opportunities for error, so whatever your library can do to help trace brain farts is time and effort well spent.

      I agree with what you've said. You're right, every developer makes mistakes, and bugs are rooted in opportunities for error. If a library can easily eliminate certain opportunities for error with minimal overhead, then it should probably do so. I'm a huge fan of C's assert() macro because it falls in line with the idea of minimal overhead (no performance penalty except when debugging). This doesn't mean that the library has to be bullet-proof. Library functions can accept their limitations and document them accordingly. It sounded like you wanted every function in the library to validate all input and define its behavior in all cases. I generally favor doing that only if the input "makes sense", but even if the function did not have well-defined behavior when the input was not handled by the function but "made sense" to me, I wouldn't curse it as long as it was clearly stated in the documentation.

    21. Re:Crashing != bug by lostchicken · · Score: 1

      I write a compiler that segfaults upon seeing any errors. It that the "correct" way of handling it? Shouldn't the compiler just expect to see good code, all the time?

      Well, for web developers, a browser is a compiler.

      --
      -twb
    22. Re:Crashing != bug by jbolden · · Score: 1

      You are somewhat attacking a strawman. I think there are really two levels here:

      1) It is generally possible to add error checking to a library at very little additional performance cost

      2) Any software company that does not provide error checking for all functions in its libraries should be shunned.

      You are arguing for #1 the original poster was arguing for #2. I gave the standard library as a well respect and well known example of a library where many functions don't have error checking (i.e. I was showing #2 to be false). I have no problem stating that I think #1 is true.

    23. Re:Crashing != bug by Anonymous+Brave+Guy · · Score: 1
      I guess I look at maintenance and integration issues in development, more than some people do, because of my background in DVT and QA.

      For the record, that library software you reckoned should be shunned goes through the most extensive set of automated tests I've ever seen every night. Every new feature and every bug that gets reported get their own test(s), and the slightest change in the huge amounts of diagnostic output produced is cause for concern and investigated. Many of our algorithms get mathematically proved for correctness before being allowed into the code. We have pretty decent coding standards and people discuss changes with colleagues to get second (and third...) opinions before modifying things. Some of our clients even get pre-released versions, to check the integration works with their software before the final product ships. Basically, the chances of finding a genuine crash bug -- or even a logic error giving the wrong answer, for that matter -- in our library if it's used as the documentation says it should be is almost zero. On the rare occasions it does happen, a bug fix is often shipped to the affected client(s) the same day.

      Now, if you're a guy who knows about QA, you should appreciate that these standards are higher than almost anywhere in the software development industry. They have to be, given the number of different clients who use our library in their product, and the number of our clients' clients who therefore depend on it. If you still think software like this should be shunned in favour of something that runs a bazillion times slower but that happens to catch some (not all) of the bad input cases you could give it, that's up to you, but I suspect the vast majority of professionals in the field would disagree with you.

      Again, I'm speaking only for myself here, and not my employer.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    24. Re:Crashing != bug by Anonymous Coward · · Score: 0

      A lot of software is written in an environment where it is reasonable to trust your sources

      No, it isn't. User input is never trusted.

      Trust (in this case) has a very specific meaning - that you know that the input will contain what you expect it to.

    25. Re:Crashing != bug by Anonymous+Brave+Guy · · Score: 1
      A lot of software is written in an environment where it is reasonable to trust your sources
      No, it isn't. User input is never trusted.

      If you'd bothered to read the rest of this thread, you'd have spotted that we're not talking about end-user software here, but libraries. And in that case, yes, it is.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    26. Re:Crashing != bug by Reziac · · Score: 1

      I don't mean account for all possible situations (which is clearly impossible, Turing aside). Just do something *predictable* when confronted with garbage data. Such as some harmless default "sorry, your bad, try again" action, instead of trying to ACT on the garbage data.

      Frex, Wildcat BBS truncates out of bounds input by the user, no matter what sort of junk it is, and always treats text fields as text, period. You can input garbage all day long and it will just ignore you, or spit you back to the main menu.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    27. Re:Crashing != bug by Reziac · · Score: 1

      True, but since that's where I am, I can only report from here...

      OTOH, by its own claim, Mozilla isn't written for end-users either, and it's a long way from my idea of reliable (I'll optimistically add "as yet").

      And I could say a few choice words about one particular compiler, and that's not exactly end-user stuff either.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    28. Re:Crashing != bug by NickFitz · · Score: 1
      Just do something *predictable* when confronted with garbage data

      The point surely is that you can't always know for certain whether input is dross or not. The poster was talking about a mathematical library; the process of establishing whether or not the input to a function is outside the set of valid inputs is in at least some cases identical to the process of doing the calculation, or so burdensome as to be unreasonable.

      Consider the case where a function requires an input point to be a member of the Mandelbrot set. Do we really want it to test every point entered? But I can still make this function available if I specify in the contract for my function that points must be such.

      If a client of my library function specifies a point outside the Mandelbrot set, and my function thus goes into an infinite recursive descent, that is the fault of the client, for breaching the contract. I could iterate over every input point to see if it is a member of the set, but consider the performance hit. Whereas a client application can happily restrict user input to a known range of the Mandelbrot set.

      The point is that code shouldn't necessarily be proof against all invalid input; it should fulfill its side of the contract, and that is all. If people want to use it wrong, that's their fault. Let the caller beware!

      It really comes down to GIGO. The purpose of a library is to offer functionality; it is up to the client of the library to ensure it does not crash it with dross.

      Just my 0.0124704 GB pence worth (~= 2 US cents at current exchange rate)

      --
      Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
    29. Re:Crashing != bug by Reziac · · Score: 1

      Well, when you get into specialised software with esoteric input, it would get damned difficult to validity-check all the data, for sure. But such programs aren't in such wide use that they impact everyday life, either. OTOH, browsers, office software, and other such common-as-dirt apps that use reasonably predictable data should be a lot easier to protect against bad input.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    30. Re:Crashing != bug by NickFitz · · Score: 1
      browsers, office software, and other such common-as-dirt apps that use reasonably predictable data should be a lot easier to protect against bad input

      Agreed. On the other hand, given that I can make a webserver pump out any file I want, with whatever MIME type I wish, it's damn hard to catch everything. As has been mentioned elsewhere on this topic, the file causing the crash isn't any kind of valid HTML, even though it starts out looking like it might be. It isn't even wrong; it's garbage. Does seem a shame that IE manages to crash rather than catch the exception, but it's not as easy to vet input as it sounds when it could be literally any sequence of bytes whatsoever. At least it should be easy enough for MS to patch; unoirtunately that will probably cause even more problems ;-)

      --
      Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
    31. Re:Crashing != bug by Reziac · · Score: 1

      I played with the file in Netscape, and while it displays an input box (rather surprising at that), that's ALL it does. No crash, no misbehaviour. Better than IE's illegal operation, for sure. (Of course I had to try it, didn't you? :)

      Yeah, you can't catch everything, but geez, IE, at least make an effort!

      One of the things our BBS's homegrown spam filter looks for is invalid MIME types -- gets rid of a lot of infected attachments. If it can't at least call itself something valid, why should we let it past this first test for valid data? :)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  168. Browser crashes shouldn't matter by Anonymous+Brave+Guy · · Score: 1
    Are we *that* confident in the maturity of our web browsers that causing a browser crash is nowadays considered a serious issue?

    It shouldn't matter.

    Browsers and the technologies on which they are fundamentally based were designed to allow the display of textual information in a somewhat formatted way. If the browser crashed, you should lose nothing but the page you were looking at, which you should be able to redisplay or display in another non-crashing browser just by opening up the address again.

    The only reason browsers crashing matters now is because the industry has warped the technology and now tries to use it for totally unsuitable things. Browsers were never meant to be part of distributed applications where real data gets shifted around. The fact that so many apps now use a "browser" front-end is indicative of nothing but a poor choice of tool, as is the fact that crashes matter.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:Browser crashes shouldn't matter by Reziac · · Score: 1

      That's yet another reason I still prefer an old browser (NS3.04): when it does fall over, it never takes any other app with it. And it almost never takes Windows with it either. Doubtless both because NS3 doesn't muck about with the OS at all.

      I agree with you about browser front ends... they're overused in all sorts of inappropriate places. Frex, a friend just got a new LinkSys switch -- and to access its configuration requires a JAVASCRIPT-ENABLED browser. Does anyone else see the problem with requiring js to control a device that's supposed to be part of your security and networking chain?? It makes me damned nervous.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    2. Re:Browser crashes shouldn't matter by jbolden · · Score: 1

      The fact that so many apps use browsers as a front end is indicative of the fact that Windows and Mac did not support the X protocol so there wasn't a reasonable graphical application interface for use with clients that don't involve installing software.

    3. Re:Browser crashes shouldn't matter by Anonymous Coward · · Score: 0

      Nice troll! You almost had me fooled for a second ;)

    4. Re:Browser crashes shouldn't matter by Anonymous+Brave+Guy · · Score: 1
      I agree with you about browser front ends... they're overused in all sorts of inappropriate places. Frex, a friend just got a new LinkSys switch -- and to access its configuration requires a JAVASCRIPT-ENABLED browser.

      Absolutely. Was there something wrong with providing a control app and a simple protocol to set it up, as everyone always used to?

      A company I used to work for produced, amongst other things, control software for networking infrastructure, and web apps. I imagine that had they ever been asked to do both at the same time, someone would have suggested this might not be a good idea(!).

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    5. Re:Browser crashes shouldn't matter by Anonymous+Brave+Guy · · Score: 1
      ... so many apps use browsers as a front end is indicative of the fact that ... there wasn't a reasonable graphical application interface for use with clients that don't involve installing software.

      There still isn't. That's kinda the point. :-)

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    6. Re:Browser crashes shouldn't matter by jbolden · · Score: 1

      The past tense was in reference to the fact that Macs now do support X and if rumors hold by 10.3 it will be part of the OS.

    7. Re:Browser crashes shouldn't matter by usotsuki · · Score: 1

      You know, there *are* XFree86 subsystems for Windows and MacOS X...

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    8. Re:Browser crashes shouldn't matter by jbolden · · Score: 1

      Sure but they aren't standard on client machines. Getting someone to install is what web based client technologies avoid.

    9. Re:Browser crashes shouldn't matter by Reziac · · Score: 1

      I suppose Linksys' objective was to have the control interface be accessable via TCP/IP, so you could get to it from anywhere on the network *or* from a remote location -- okay, reasonable enough if you're the network support guy and can't hop a plane to corp HQ every time it needs your attention. And there's usually SOME browser available, or can be acquired quick (if all else fails, carry Mosaic or NetTamer [DOS internet suite] around on a floppy!) But whose to say that you've always got ACCESS to a js-enabled browser, even if that were totally safe?

      And what really bothers me, how do we know the switch's js doesn't have an exploitable hole?? So if it's going to use a browser interface, it should be the simplest one possible, to ensure accessability and security.

      Everything doesn't need to be the bloody kitchen sink!

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  169. Agreed: Tested with IE 5.2 for X by HotButteredHampster · · Score: 1

    Damn. I thought that would be something fun to see, but now I have to wait until Monday when I can crash IE at work.

    Note to Microsoft's Mac BU: please stop writing software which is better than the Windows stuff. It makes making fun of you less sweet.

    --
    "Smart is sexy." -- D. Scully ("War of the Coprophages")
  170. clearly this is on purpose by claude_juan · · Score: 0, Redundant

    it may just be me, but it seems that this was thrown in intentionally by a code monkey, probably for error checking. so chill out. or better yet, make sites that take advantage of it! i dont know about you, but i get pretty pissed at those sites that require certain browsers, plugins, etc. this is your chance to make the windows world use something *better* (mozilla, phoenix, etc). web developers unite!

    1. Re:clearly this is on purpose by Anonymous Coward · · Score: 0

      Good idea. Do something like this in every page:

      <script language="javascript">
      <!--
      if ((agt.indexOf("msie") != -1){
      document.write('<input type crash>'
      }
      //-->
      </script>

  171. Opera is not affected by any of this by Bazouel · · Score: 0, Redundant

    I tried the code of the article and various piece of code given in comments and nothing can make Opera crashes or even make it behave funny.

    Yet another reason to use it !

    --
    Intelligence shared is intelligence squared.
  172. Large GIFs can do it to by dwsauder · · Score: 1
    There's this one from Jef P. Check it out http://www.acme.com/jef/killer/crash.html
    This is just a very large GIF. It's a single color, but is thousands of pixels on a side. In GIF form it compresses down to only a few kilobytes, but when your computer tries to uncompress it for display it balloons out to a whole bunch of megabytes. At the very least your system will take a long time to do the uncompression and display, during which time it will be unresponsive. Most likely your browser will run out of memory and fail to display the GIF, possibly exitting. Some people report that their computer actually reboots.

    If your system is robust enough to actually display this text and not lock up, well, congratulations!

    By the way, I had to write a custom program to produce a GIF this big. The standard GIF writers crapped out on sizes that could still be displayed.

    My PC handles this page without a problem. It might cause problems on older PCs. Of course, you could always put more than one such GIF image on a page.

    1. Re:Large GIFs can do it to by Zarf · · Score: 1

      If your system is robust enough to actually display this text and not lock up, well, congratulations!

      Yay for me! BTW: Go to the top of the dir ( http://www.acme.com/jef/killer/) first 'cuz the web master very wisely put "referrer protection" on the page and you can't get to it from an outside link. My version of Mozilla handles this page fine but my version of Konqueror got a little bogged down trying to render the page. I'll bet there are browsers out there that would indeed totally choke on that teeny tiny little gif... only 33k file size and I watched it consume nearly 200MB of memory to get rendered in Mozilla. Now that's entertainment!

      BTW: for those of you whose browsers can't render the image... it's a black gif background image of 7000 by 7000 pixels.

      --
      [signature]
  173. None of my Java Apps ever crashed. by Anonymous Coward · · Score: 0

    Javigator works like a charm!

    1. Re:None of my Java Apps ever crashed. by Anonymous Coward · · Score: 0

      Too bad that Java is closed source and proprietary. Fortunately, there will probably be a Mono-based browser in the not-too-distant future.

  174. Current example Mozilla crash by ratpick · · Score: 1

    Just go to ebay, and do some advanced searches. Mozilla 1.1/win2k, on my machine anyway, won't last more than about 2 or 3 searches--really. Crashes hard _every_ time I forget to use a different browser. The first time I tried to let it generate and send the error log, but that locked up as well. In general, however, my past experiences have favored navigator about 10 to 1 over IE.

    1. Re:Current example Mozilla crash by Anonymous Coward · · Score: 0

      oh gawd, Navigator is the WORST browser I've ever used. The original Mosaic is more stable than that piece of shit software.

    2. Re:Current example Mozilla crash by pointym5 · · Score: 2, Informative

      The 1,3 version seems to fix all the ebay crash problems.

    3. Re:Current example Mozilla crash by elemental23 · · Score: 1

      Ebay works fine for me with any version of Mozilla I've ever used (starting at 0.9.3) on Win2k. That's browsing, buying, and selling.

      The early 0.9.x versions had trouble with the JavaScript Ebay uses on their auction listing forms, but it never caused a crash and it's been working fine for well over a year now. I don't know if that was a Mozilla problem fixed in a later release, or a JS bug eventually fixed by Ebay.

      --
      I like my women like my coffee... pale and bitter.
    4. Re:Current example Mozilla crash by Anonymous Coward · · Score: 0

      I reported that bug several months ago - it was caused by very poor non-escaped SIZE tags. In other words it scaled fonts so large they used up enough free resources to crash the application.

      Just use Mozilla 1.3 or even better Phoenix 0.5.

  175. It crashes with other input "types" by rollingcalf · · Score: 2, Informative

    You don't need to specifically put "input type crash", as something like this also crashes IE:

    <html>
    <form>
    <input type abc123>
    </form>
    </html>

    --
    ---------
    There is inferior bacteria on the interior of your posterior.
    1. Re:It crashes with other input "types" by YodaToad · · Score: 1

      Actually, the HTML doesn't even need to be well-formed.

      You can just do:
      <input type blah>

      as a single line and it'll do the same.

    2. Re:It crashes with other input "types" by man_ls · · Score: 1

      That's cuz the proper syntax of an INPUT tag is:

      INPUT TYPE CRASH...the crash is an invalid attribute, and the TYPE is missing its parameter.

      You have massively malformed HTML there, so of course it's going to crash...I guess IE is just a little less careful for looking for the way to render something that doesnt exist than some other browsers are. But, this isn't an MS problem...

      You've got to remember that HTML is still a programming language. If you write bad code in C/C++ you can take down your OS with memory leaks, overwriting your command stack, etc. In HTML, you can crash your browser.

    3. Re:It crashes with other input "types" by TeddyR · · Score: 1

      The issue is that a browser should NOT crash even with bad html...

      A browser should ignore all items it does not "know aout" or understand....

      --

      --
      Time is on my side
    4. Re:It crashes with other input "types" by Tsu+Dho+Nimh · · Score: 1

      Any unrecognized input type will work, or none at all. The browser should NOT croak over bad HTML, it should just skip it and go on to the next tag.

    5. Re:It crashes with other input "types" by man_ls · · Score: 1

      Your compiler will not produce code with instructions it does not recognize.

      It will produce executable code with instructions it recognizes, ordered in such a way as to produce bad effects, intentionally or not, due to the way they are laid out.

      For your all information, this bug has absolutely nothing to do with the third parameter. The problem exists when only run as

      INPUT TYPE

      with no attribute value, or any additional text.

      So, chalk it up to subpar error handling...This bug could be analogous to a double free() or a pointer being reassigned to the wrong target. Just because the compiler (browser) doesn't catch it doesn't mean it's the not the programmer (page creator) fault.

  176. This is for debugging by shodson · · Score: 1

    I can imagine the IE developers put this in there for their testing purposes, like for testing their automated bug reporting software. They probably just forgot to take it out.

  177. What if... by dumboy · · Score: 2, Funny

    MS did it on purpose for debugging purposes? Maybe a couple more tags like
    <input type bluescreen>
    <input type slow_machine_to_crawl>
    <input type bsa_audit>
    <input type flood_ISP>
    exist and they just haven't been discovered yet.

  178. Crashes desktop in auto-preview!!! by Anonymous Coward · · Score: 2, Interesting

    Just for grins, I saved the file, and now can't delete it (without mucking around) due to the fact that the whole desktop crashes while IE tries to render the little thumbnail of the page in Exploder. And no--I don't have active desktop enabled.

    Fun for the whole family!

  179. IT's Worse than just this. by Anonymous Coward · · Score: 0

    Try to play .mpg or .mpeg files by clicking a link on a page and that seems to crash the current WMP 9 unless you save the file to disk first. STRANGE it doesn't affect wmv files.....fucking MS dickheads

  180. Re:Phoenix by Jugalator · · Score: 1

    OK, so that's another thing IE for Mac excels at then. Yes, it's more standard compliant as well, although IE 6.0 for Windows caught up a bit.

    --
    Beware: In C++, your friends can see your privates!
  181. This is not fair by unborn · · Score: 2, Funny

    Why do Windows people get all these features. I don't even have a way to test it. Damn you Microsoft Monopoly. Damn you Konqui for refusing to crash when most needed.

  182. no prob with Konqueror by The+Tyro · · Score: 2, Interesting

    it shook it off just fine.

    --
    Even if a man chops off your hand with a sword, you still have two nice, sharp bones to stick in his eyes.
  183. Um so what.... by Anonymous Coward · · Score: 0

    Hell having IE crash and close a window on an HTML page that simply is not ever going to appear in the real world, whats the big deal? With the userbase IE has, the odd crash bug is really not a big deal at all. When I first used NetScape on RedHat Linux I managed to make it crash 5 to 6 times, one of which also took down part of the windowing system on KDE, which made the Titlebar and window controls disappear on all the windows I had open, only a reboot resolved it (oh yeah I had to call someone down from IT support to reboot it as the Linux machines are so tempromental that they dont always boot properly). the only difference between crashing on Linux and Windows is Linux just kills the window and says no more, at least windows keep you informed with a dialog box telling you that something happened.
    I'll stick to IE, it works, its free, its the standard. If Netscape and others want to compete with it, heres some advice; make your browsers at least as good as IE before trying to get users to migrate to it.

  184. Windows Bugs by HappyHour · · Score: 0

    Much too much time is spent on documenting the bugs in Windows. Resources are much better allocated elsewhere. Anyone who must deal with Windows knows that the easiest way to expose a security or reliability issue with this OS is to boot a Windows PC. Sheesh!!!

    1. Re:Windows Bugs by Anonymous Coward · · Score: 0

      The reason is deeper than that. It is not that anyone cares about Windows. It is so we can say "Fuck You" to Microsoft and prove to them how much better Linux is. It is a superiority issue.

  185. Fuzzle Horsey? by Anonymous Coward · · Score: 0

    Fuzzle Horsey!

  186. sig? by (startx) · · Score: 1

    I think I just found my new email sig :-)

  187. Mail-A-Crash by Anonymous Coward · · Score: 1, Interesting

    Things becomes interesting with these lines from SecurityFocus.com..

    "This HTML also crash Outlook, Frontpage, and all the Microsoft programs that use the shlwapi.dll library to render web code."

    ..so basically you can push a remote crash message to users of Outlook. All they have to do is look at your message, and the program crashes? Anybody got sacked and wanted to get back at their company, this could provide an opportunity to do that.. ..just email all users in the company directory.

    1. Re:Mail-A-Crash by Anonymous Coward · · Score: 1, Insightful

      Anybody got sacked and wanted to get back at their company, this could provide an opportunity to do that.. ..just email all users in the company directory.

      Yeah, and make sure you let /. know beforehand, so we can follow the progress of the lawsuit your company will file against you for doing this-- if they can't manage to get you arrested for it first.

  188. IE Mac is fine by DuckWing · · Score: 1

    IE on Mac OS X is fine, no crash. So is pretty much any and every browser based on Geko.

    --
    -- DuckWing
    1. Re:IE Mac is fine by Anonymous Coward · · Score: 0

      Since when is IE based on Gecko? That is a technology developed by Mozilla. It is used in Mozilla, Netscape, and other browsers. But, M$ would sooner use Gecko... as they would shove hot nails up their ass.

    2. Re:IE Mac is fine by KefkaFloyd · · Score: 2, Informative

      You need some reading comprehension skills. He meant that in ADDITION to IE.

      --

      Conglom-O: We Own You (TM).
  189. Would thid be proof ... by Anonymous Coward · · Score: 1, Funny

    that IE is part of the O/S?

  190. Mod parent funny! by Anonymous Coward · · Score: 0

    That's beautiful. Can you say "Mailinglist Archives"?

  191. Re:Phoenix by p51d007 · · Score: 1

    Exactly! IE crashes because 80+% of the dopes out there use IE. True geeks use a good browser, like Mozilla, Opera, Phoenix, et al.
    Problem though, just like linux, once enough people start using the alternative browsers, the people who find "bugs" like this, will start looking for ways to comprimise them. But, unlike M$, the open source community will squash them quicker, without waiting for 1000 meetings to determine how to fix it.

  192. my paranoia says by hhknighter · · Score: 1

    this sounds more like a command to me

    I mean, "input type crash", the word crash just got my M$ suspicous deeds rolling.

    Maybe this is a special pre-XP era piracy battle scheme. When users update their version of Windows and the CDkey or serial key appears to be jacked, they divert you to a "NEW" page, crashing your IE. Average joe might think, "oh no, must be me pieratted windose, gots to got me a real cupy instead"

    sarcasm was seriously intended

  193. $100 ??? Where did you buy it? by mgkimsal2 · · Score: 1

    That is in a consumer OS (XP Home) that costs less than $100...

    http://www.microsoft.com/windowsxp/pro/howtobuy/pr icingretail.asp

    $299 as I read that page...

  194. XP integrity demonstration by iFlynn · · Score: 1

    Of course whenever MS is mentioned on /. everyone has to jump on the bandwagon and start taking pot shots, but in this case I feel it has backfired.

    I've been using XP since its release and from the start I've enjoyed the overall system integrity it provides. I can't say that IE has never crashed before on me, but it has been very rare and I surf dozens of different sites every day. One thing I had noticed in the past, but wasn't entirely sure about until now, is that if a page crashes IE then it only shuts down the window that page was in.

    With this bug I was able to test this and found it to indeed be the case. With several IE windows open I clicked on the link in one of them and only that window crashed.

    Since no browser in the world is immune to crashing, this bug is more a testiment to the integrity of XP than a an example of bad programming in IE.

    Let's face the facts, there have been many examples of real problems that have been found in IE that actually have potential for danger, this is not only minor, it borders on nothing. HTML is code right? Code is written by programmers right? Should not the integrity of the code be the responsibility of the programmer? You point the finger at the MS programmers because their code won't handle every possible code error of another programmer?

    Have you ever written code that crashed? What did you do, debug your code or start firing off letters to /.?

    1. Re:XP integrity demonstration by Anonymous Coward · · Score: 0

      Microsoft still sucks donkey dick... don't kid yourself. Penguins will rule the world someday.

    2. Re:XP integrity demonstration by hnoon · · Score: 1

      As stable(r) as XP is, your one window crash happens on Win98 too. I just tried it. (I could be wrong but it makes me think that it is coded into IE.)

  195. Humor within M$? by AblativeCoating · · Score: 1

    "" Is this some kind of a joke? You crash the app simply by putting in "crash." Priceless!

    --
    TANSTAAFL: It's not just a good idea, it's the law.
  196. Crasher warning by edsel · · Score: 2, Insightful

    I just noticed that the tantek.com link I posted above crashes Webcore-based browsers. After posting the comment from OmniWeb 4.5 (which uses KHTML Webcore) I clicked on the link. OmniWeb crashed.

    Since I'm using a "Sneaky Peek" version of OmniWeb, I thought that maybe it was just a bug in the beta code. I tried the same link in Safari and it crashed too.

    I assumed that since this was a page on Tantek Çelik's site the CSS would be valid. The page flunks the HTML validator at w3c.org because of a misplaced noscript tag. - I wouldn't expect that to crash a browser.

    Must be a WebCore bug. Kind of ironic given the topic.

    1. Re:Crasher warning by Anonymous Coward · · Score: 0

      Exactly right. Nice discovery.

      Good thing it's insanely easy to report such bugs.

    2. Re:Crasher warning by Anonymous Coward · · Score: 1, Funny

      Proffesor Fink: "My sarcasm detector is going off the scale!"

      Comic Book Guy: "Yeah like thats a useful invention"

      (Sound of exploding Device)

  197. NULL pointers and error handling by _xeno_ · · Score: 5, Informative
    Actually, under Windows and UNIX and almost every OS I know about memory location 0 is mapped. It's mapped to the kernel. (Hense the talk of "user space" vs "kernel space".) Attempting to read or write to this location will cause an access violation on the resulting page fault, whatever the OS chooses to call the error. UNIX calls it a segmentation fault, and Windows calls it a general protection fault. (XP calls it "a problem.")

    This is a good thing. NULL is generically used to indicate that a pointer is invalid. Attempting to read or write to a NULL pointer is always a bug and should cause the application to be stopped. Writing and reading from random memory address is a sure fire way to cause interesting results. Enforcing such restrictions helps to force programmers to ensure their programs are at least less buggy in that respect.

    MacOS 9 allowing location 0 read/write is a bug, not a feature. (Well... probably not, really. MacOS 9 and prior probably allowed 0 as a valid userspace location.) When a program attempts to read or write to NULL, it should be terminated, as this is an error condition. This would be like ignoring the low oil pressure light on your car - you might be able to keep running for a while, but disaster could strike further down the road.

    --
    You are in a maze of twisty little relative jumps, all alike.
    1. Re:NULL pointers and error handling by t · · Score: 1

      Memory location zero is only mapped to zero on some architectures and then only when there is no virtual memory. With VM, every process can have memory addresses that appear the same but correspond to different physical pages of memory, i.e. the address is meaningless outside of the process.

    2. Re:NULL pointers and error handling by Thing+1 · · Score: 1
      This would be like ignoring the low oil pressure light on your car - you might be able to keep running for a while, but disaster could strike further down the road.

      OT but true story: I had an old car on which the idiot light blew out. So I didn't know I was running low on oil, and BLAM -- $2,000 engine rebuild job. Ahhh, high school memories.

      --
      I feel fantastic, and I'm still alive.
    3. Re:NULL pointers and error handling by gobbligook · · Score: 1

      memory location 0 does exist. It has to, since all computer systems work on the binary system. Not because there is no virtual memory or some such thing.

      logically memory location 0 could be called "beer4Me" that's just a label. The fact is the memory location exists, is useable (by the os) infact I could be mistaken but isn't it a check bit of some sort?

      Null pointers do not point to a memory location. That is the whole point of the word NULL. They are pointers to NON-EXISTANT memory locations.

      you ask, "how can a memory location be non-existant? isn't that like saying this beer I am drinking doesn't exist?" The other way to think of this is the null pointer is a pointer to an automatic garbage collector. The collector is never full, never empty, just a black hole.

      They fool the application into thinking it is sending instructions/data somewhere useful. Just because you have one null pointer does not mean you can't have more, or that you can't create one and name it "PoorCollegeStudentBankAccount" either.

    4. Re:NULL pointers and error handling by Anonymous Coward · · Score: 0

      Nor are you expected to get your panties in a knot. Safari is still beta. Internet Explorer, however, is an established browser with years of development behind it. See the difference?

      As for your thoughts on "the way Mac people think," I don't think most Mac people (in the OS 9 and earlier) era really cared. The sad fact is that OS 9 (with applications having the ability to stomp on other processes) was actually "pretty stable," all things considered (especially compared to a certain operating system developed by Microsoft). Quite a feat when you think about all the ways a programmer could accidently bring down the system.

      But all of this is history now anyway. Mac OS X obviously has protected memory and applications certainly don't bring down the OS, nor does Apple even suggest a restart when an application does crash.

      Windows is a different story. Although with Microsoft's funds you would think they could make a version of Windows that doesn't crash (and XP is getting closer), there just isn't one yet. Pathetic, really (in my opinion) but that's for another discussion.

    5. Re:NULL pointers and error handling by Krach42 · · Score: 2, Interesting

      OS1-9 used a non-protected memory model. There was no virtualized memory, because every application worked in the same memory space. And actually, this is nearly the same way that Win9x worked. Thus, the recommendation from Microsoft to reboot the entire system if a program crashed in 9x.

      --

      I am unamerican, and proud of it!
    6. Re:NULL pointers and error handling by t · · Score: 1

      Null pointers and a ptr with value zero are equivalent. In some situations it is valid to use a pointer with value zero, but usually not. This is not because of some kind of fundamental problem with it, but solely because of the ease of making a programming error.

    7. Re:NULL pointers and error handling by HiThere · · Score: 2, Funny

      And this is a part of why idiot lights are a really inferior replacement for gagues. If the gague died, you could tell immediately, as it needle dropped to the bottom (or pegged the top).

      Another vile interface with idiot lights is the one that has an indecipherable light. Several mechanics have not been able to figure out what it means that one idiot light in my car sometimes comes on. One time it was fixed for about a week by adding oil (the oil light didn't come one, but when I checked the dipstick it was v. low). The owner's manual is... inscrutable.

      Now, how to tie this back to null pointers... null pointers are sometimes 0 values that get stuck into pointers by accident. I don't think I've ever seen a good valid use of a null pointer as a pointer. But it's the default initial value (when there is one). So null pointer references *should* be disallowed. But I've encountered bad valid uses of null pointers. I've seen code where location 0 was used to store a value that needed to be globally accessible. (This may have been on a Z80, or some such.) Now that was a bad valid use of a 0 pointer, but it did allow code to be relocated. The problem was, if you encountered a pointer, you couldn't tell the difference between a null pointer and a 0 pointer. This lead to many troublesome errors. A far better choice is to just disallow it.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    8. Re:NULL pointers and error handling by Anonymous Coward · · Score: 0

      I think part of the reason OS 9 apps were relatively decent is that if a programmer made a single mis-step, it would crash the app and possibly the system, therefore newbie Mac programmers quickly learned what NOT to do.

    9. Re:NULL pointers and error handling by bhtooefr · · Score: 0

      Look at your German textbook... Null means 0 in German.

    10. Re:NULL pointers and error handling by Pyrion · · Score: 2, Insightful
      Unless you have something like MS Visual Studio installed, in which case it comes up with something like...

      The instruction at "0x70a71927" referenced memory at "0x00000000". The memory could not be "read".
      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    11. Re:NULL pointers and error handling by poemofatic · · Score: 1

      Safari is beta software (yes, it does crash a lot) that users may download from Apple. IE is a flagship MS product that is bundled with the OS, and is integrated into the windows explorer gui (and into the kernel). This accounts for the panty moisture difference.

      --

      When in doubt, have a man come through a door with a gun in his hand.

    12. Re:NULL pointers and error handling by Anonymous Coward · · Score: 0

      It's mapped to the kernel

      Please correct me if I am wrong, but kernel also wants to trap a NULL pointer reference; isn't it that the first page is always non-existent in order to catch those NULL pointer addresses ?

      UNIX calls it a segmentation fault, and Windows calls it a general protection fault

      Not to be nitpicking, but I think Intel calls it a general protection fault. A segmentation fault is a general protection fault that has to do with accessing memory beyond the segment boundaries; this never happens in flat memory OSes since the segments are not used and are 0xFFFFFFFF in size. A general protection fault actually is interrupt 13, isn't it ?

      Finally, does anyone remember the famous

      printf("\n\n\n\n\n\n");

      bug (or something like that, I am too lazy to dig it up) ? the programmer could halt Windows NT. Of course, it is fixed a long time ago, but it was an important one.

    13. Re:NULL pointers and error handling by Genyin · · Score: 1

      So null pointer references *should* be disallowed. But I've encountered bad valid uses of null pointers. I've seen code where location 0 was used to store a value that needed to be globally accessible.

      They are. Or, at the very least, what happens is not well defined. It is certainly not remotely portable to be writing or even reading from null.

  198. EXCEPT this is supposed to work with outlook etc.. by aepervius · · Score: 1

    After all it is using all over the in windows explorer rendering enginer.

    --
    C. Sagan : A demon haunted world:
    http://www.amazon.com/gp/product/0345409469/
    visit randi.org
  199. Re:battle.net forums by Anonymous Coward · · Score: 0

    Go to the battle.net forums, select, say, Diablo II Hardcore forum, then open several links in tabs. That pretty reliably crashes gecko for me.

  200. Entourage and Exchange don't play nice by Karl+Cocknozzle · · Score: 1
    the Entrouage email/calendar/pim app is a lot more sane than Outlook (though is lacking full Excange integration).

    It is interesting to me that we don't hear more complaints about this rather large shortcoming. You could almost say Entourage effectively cripples replacing a lot of PCs with small, reliable iMacs, since many companies depend on the groupware functionality of Exchange/Outlook. If Entourage can't provide that to the Mac users, there won't BE any enterprise mac users--or at least, any enterprise Mac users that don't also have to have a seperate PC with its inherent Windows License and extra Exchange CAL, and Office license.

    Since I always use my Mom as a "Joe/Jane Average" computer user example, lets pretend her office wanted to go entirely Mac tomorrow on the desktop, but still keep their Exchange server and domain controllers running Win2k.

    Their custom business apps are actually terminal sessions on a couple of unix boxes, and their ERP/Purchasing system is provided via web-interface.

    They could do it, except for one freakin' problem. They "need" (psychologically, not in reality) their groupware to be MS Exchange compatible because it would be "too hard" to switch to something else. But entourage doesn't do that. So they're screwed.

    Sure, they could ditch the calendaring through exchange and setup an intranet apache server with everybody's iCal calendar published to it--it would be pretty neat and not involve any more damn CALs. But the mental hurdle of non-tech users in positions of authority to jump is sooo hight--and MS knows this.

    Sure, they've "announced" that it will eventually work. "Eventually". But does anybody really expect it to be flawless? Without a single, solitary, "red-headed stepchild" workaround or hack to make it work right?
    --
    Who did what now?
    1. Re:Entourage and Exchange don't play nice by extra88 · · Score: 1

      Entourage is already a good Exchange client for email and server-side contacts if LDAP and IMAP are enabled on the server. Yes, group calendaring is still the big missing piece, one which is supposed to be filled in this summer. Currently Mac Exchange clients have to use Outlook 2001 which is a big improvement over its predecessor but still pretty crappy and half-assed. Outlook 2001 was written by the Exchange group, not MBU. The announcement that Entourage would be the Exchange client was good news not only because it meant there would finally be an OS X native client but also because its the MBU doing it, not the Exchange group.

      You're iCal suggestion wouldn't replicate some of the most useful features. Could you create an event on your calendar and have it sent to who ever else should be there and let them Accept or Decline it and have that action not only send you a reply (so you know if they're coming) but also automatically add it their calendars? Okay, that one might actually work, I'm not sufficiently familiar with iCal capable clients.

      Even better, with the iCal option, how do you take a list of 7 people and with the click of a button, find the first hour all 7 are free this week? How do you get all 7 calendars displayed, one person per line, to look for yourself when they're free? Sure all of these *could* be done using iCal published calendars, because the data is there, but it would be totally client dependent, it's not a part of any standard. iCal is client-oriented, it assumes that the client is the primary storage location for calendar information. That's fine when you're doing personal calendars but in an organizational setting, the data and some of the connections made between data sets should be on the server.

    2. Re:Entourage and Exchange don't play nice by Anonymous Coward · · Score: 0

      Yes, an iCal client has to do all these, but there's nothing to stop that client from being server as well.

      I'm not very familiar with iCal, but would, for example, importing all 7 published calendar into "client" (php web application), and have it list its "own" free time work?

  201. Even worse for Opera by gregorio · · Score: 0

    http://www.securityfocus.com/archive/1/319621/2003 -04-20/2003-04-26/2

    Opera crashes to the point where you have to *reinstall* it so you can run it again.

    All you have to do is run a very large 'news:' URL.

    1. Re:Even worse for Opera by TitanBL · · Score: 1

      Ya, but does Opera does not crash on command...

  202. Re:Phoenix by Anonymous Coward · · Score: 0

    Is that true? Why aren't the hardware specific bits abstracted out, so that a common codebase can target arbtitrary operating systems.
    Wait: the subject is Multiple Sclerosis. Never mind. Monopoly, Someone?

  203. WMP by Draconix · · Score: 1

    True enough, but who actually uses WMP on a mac when there's VLC and Mplayer? Come on, people, opensource, opensource!

    --
    By reading this you acknowledge that you have read it.
    1. Re:WMP by mibus · · Score: 1

      Shame of it is not all recent WMV files can be played by them :-(

      I haven't had much luck with WMVs lately though, serious sync drifting... in both mplayer and WMP. Quite possibly the file's fault though, I'm not in direct contact with the author.

      WMP runs like a dog on some files too... when MPlayer plays them happily :-D

  204. Does it crash Outlook? by juliao · · Score: 1
    I don't run it at home, so I can't test, and it's the weekend, so I'm out of my lab, so I can't test.

    Does this bug affect Outlook? Because if it does, it's suddenly a bit more serious.

    And if it doesn't, what stops anyone from "crashing hotmail" (if you get my drift...)

  205. Even changing the filename crashes explorer. by everklear · · Score: 1

    Try saving the original link as a text file. Browse using Windows Explorer (I know, same thing as Internet Explorer...) and attempt to rename the file. Crash-o-rama. Nice one, Microsoft. So is there any possible utility of the input type "crash"?

  206. It crashed Mozilla! by Animats · · Score: 1
    I tried this with Mozilla 1.2.1 on NT 2000, and the page rendered fine. But when I did a "view source", CPU utilization went to 100% and stayed there. I had to kill the browser.

    On later tries, "view source" worked.

    1. Re:It crashed Mozilla! by falsification · · Score: 1

      WFM.

  207. Browser Bitch-Slap by louzerr · · Score: 1

    Cool Beans! It sounds like kind of a "browser bitch-slap", certainly a lot more expressive than "Microsoft-Free Fridays".

    Now what would be really cool is if you could program an ActiveX component for IE that would automatically install Mozilla - help the misinformed user, rather than just pissing them off.

    I really don't know why anyone would use a browser that can't even get HTTP right (Hey Microsoft bozos, what do you think "Content-type" means?).

    --
    "The large print giveth, and the small print taketh away" -- "Step Right Up", Tom Waits
  208. Re:Phoenix by LittleDan · · Score: 1

    you mean (input type crash) except in brackets?

  209. I might as well say it before "they" do! by callipygian-showsyst · · Score: 1
    I expect that a zillion Macintosh users will post to this thread (with rabid foam drooling from their mouths) that their Macintoshes + Safari aren't vulnerable.

    So, I'll say it here first and save them the trouble!

    1. Re:I might as well say it before "they" do! by dick+johnson · · Score: 1

      You're right. But the post is wrong. The code also doesn't crash IE 5.2 on Mac OS X. I just tried it and it didn't crash.

      Maybe it's a windows thing. I'll try it later.

      -dj

      who uses both all sorts of operating systems and doesn't foam at the mouth.

      --
      - dj
  210. No "bashing", well-earned untrustworthiness. by jbn-o · · Score: 4, Insightful
    It's a usual bug. All browsers have them.

    No, not all browsers have this bug and so far I can't replicate similar sounding bugs in Mozilla producing a crash and loss of work. Also, not all browsers are so widely used and not all browsers integrate code with widely used e-mail clients (Outlook and Outlook express still use the same HTML renderer that is subject to so many problems). This leads to multiple paths to sabotage someone remotely, perhaps even anonymously. Let's not forget that any application that embeds MSIE/Windows' renderer is vulnerable. Considering how many people use MSIE on MS Windows and how many of them are affected by this bug, I'd hardly call revealing the bug a "joke".

    This bug does *not* exist because MS is Evil.

    I'm not encouraging anyone to think in the false dichotomy of good vs. evil and neither should you. Nobody is helped by glossing over relevant details of how this works or ignoring the wide scope of the bug. This is one of a long string of Microsoft bugs that directly adversely affects ordinary users. We are much better served by suggesting real-world fixes (such as switching to Mozilla to do most browsing, even under a proprietary operating system). We're also better off identifying this exemplar of the practical shortcomings of proprietary software. There's no workaround here--MSIE/Windows users must simply wait for a fix from the proprietor if they won't switch browsers (and any other app adversely affected by embedding the MSIE renderer).

    1. Re:No "bashing", well-earned untrustworthiness. by Anonymous Coward · · Score: 0

      ...actually, it is a "joke", unless it does do something like allow other code to run. If all it does is just crash IE (and hopefully not Explorer, because you did set Explorer to run in a separate process, right?) and all of its windows, it is annoying, unless someone manages to write code that saves a page with this HTML on a computer and change that user's homepage to that file. That would be REALLY annoying. Imagine the calls to the helplines about that. Even more evil would be if it somehow broke right-clicking on the "IE" desktop icon to change IE's properties.

    2. Re:No "bashing", well-earned untrustworthiness. by Anonymous Coward · · Score: 0

      No, not all browsers have this bug and so far I can't replicate similar sounding bugs in Mozilla producing a crash and loss of work

      This is beside original poster's point. What the original post tried to illustrate is that almost all software does contain bugs, not that you can replicate this particular windows-specific IE bug in your mozilla browser. And while it is indeed true that this exposes windows/IE/outlook users to greater danger of remote sabotage, a similar problem would (and probably does) exist if a comparable mozilla bug was posted on Slashdot; most linux distributions come bundled with stacks of software that uses the mozilla engine for all things HTML.

      'Nuff said.

  211. Re:Microsoft...bleh. by Anonymous Coward · · Score: 0

    Get a modern system and run Windows XP. You'll be surprised at how much better it is than WinME.

  212. Re:$100 ??? Where did you buy it? by justMichael · · Score: 1

    umm, you do know the difference between "Home" and "Pro", don't you??

    http://www.microsoft.com/windowsxp/PRO/howtobuy/ pr icingretail.asp

  213. nice! by Erris · · Score: 1
    Whether it's my mom or another engineer, I feel pretty good about telling them XP is a solid OS that can do what they need. (likewise with IE)

    I feel the same way about Debian and Mozilla. Last time I checked you could get a CD set for $8, and it comes with more text editors and spread sheets than you know what to do with. Oh yeah, it also can't be remotly exploited as easily, has no built in spys and has no demeaning click through submissions. By the same token, I feel confined, badgered and disrepected anytime I'm forced to use M$ software and it's pathetic single screen, network unaware GUI. Some people do strange things to their mom, not me.

    --
    DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
  214. We stand in Awe of you and you potential by TitanBL · · Score: 1

    This is not a bug - it is more like an instruction/command. 'Crash on Command' - has a nice ring to it... I mean - if everything else is able to bring windows to its knees - the average user should be able too as well - right?

    "Maybe if our users realize how easy it is to crash our software they will be more understading..." Brilliant! Those guys in Redmond just never stop innovating.

  215. Re:this article makes FOSS community look like kid by Anonymous Coward · · Score: 0

    In order to beat them... we can't play by their rules. Obviously, if we did, they would kill us in seconds flat. So, we resort to "guerilla warfare" and fight them in a way that they can't defend against. In the end, the goal is the same -- "take down Microsoft and stick a red-hot poker in their eye!" The ends justify the means.

  216. 0 isn't mapped to the kernel... by pr0ntab · · Score: 2, Insightful

    On Linux and Windows, the .text segment of the currently rybbubg program starts one page AFTER 0. the page containing the address 0 is marked no-access so that NULL pointer deferences PURPOSEFULLY crash the program. They waste 4k of memory for that feature.

    Otherwise, the program would just keep going. YOu wouldn't see the crash until you attempt to write there and clobber your code.

    --
    Fuck Beta. Fuck Dice
    1. Re:0 isn't mapped to the kernel... by bullestock · · Score: 1
      Completely off-topic, but

      ...the .text segment of the currently rybbubg program...

      That's one of the funniest typos I have seen in a while.

    2. Re:0 isn't mapped to the kernel... by Thing+1 · · Score: 1

      It's encryption. Used to have a co-worker who would constantly type shifted over either left or right, he wrote the funniest code. ;-)

      --
      I feel fantastic, and I'm still alive.
    3. Re:0 isn't mapped to the kernel... by cpeterso · · Score: 1


      On Windows NT, the first 64 KB and the last 64 KB (before the 2 GB line) are mapped no-access. This is not a waste of memory because there is no page there. It is a waste of address space, though.

    4. Re:0 isn't mapped to the kernel... by Krach42 · · Score: 1

      Linux is similar. Stack starts at bffd7000, heap starts at 40000000, but so do the linked libraries, so depending on how many libraries you link it'll go up from there. The code text segment is at 8048000.

      Note it's not really a "waste" of address space, since applications will usually not use the whole address space anyways. Yeah, if you have some high memory-requirement program you're going to have trouble, but most of those programs try and keep as little in memory as possible.

      --

      I am unamerican, and proud of it!
  217. I can't wait to send this out... by The+Master+Control+P · · Score: 1

    To all my school sysadmins: "The following 5 lines of innocent HTML code will crash Internet Explorer:" That would really be priceless. "So, still want to use Windows? I've got Knoppix and Mandrake CD's if you want to try."

  218. Re:Hah! I've got something that will crash IE also by SilentStrike · · Score: 1

    No, his own OS does.

    (I actually don't know if your whole machine will crash hard with this, I don't have a machine to test it on, but there was a lot of buzz about it on flipcode awhile ago).

    This is from here.

    And finally, a non-screenshot related bug: the following neat little program, when compiled and run, will completely crash XP (and any earlier version of NT) (when I ran it, XP rebooted). I don't recommend you really try this program, but if you do, save all your work etc first:

    #include <stdio.h>

    int main (void) {
    while (1)
    printf ("\t\t\b\b\b\b\b\b");

    return 0;
    }

  219. Re:Not THAT serious... (processes versus threads) by markjugg · · Score: 1

    I believe Konqueror has this feature. It can either run different windows in different processes or in different threads.

    And in Konqueror, you can configure this behavior. Look under Settings: Configure Konqueror: Behavior.

    This is what the "minimize memory usage" section" is about. If you set it to "Always", everything runs in a single process, so it's a bit faster, but you risk losing all windows if one crashes (which they seem to rarely do).

  220. I like Tags by ari_j · · Score: 1

    My IE (6.0.etc) just crashed with only '', which is one (malformed - you should get a parse error for it) tag. The full version linked to by the story is 5 tags. Just like you can measure C in instructions such that 'a(); b(); c++;' is 3, you can count HTML by tags. The generic term is 'lines', regardless of formatting.

    1. Re:I like Tags by tinguru · · Score: 1
      I think you are right, 3 tags of HTML; 5 elements of XML, and it would be silly to argue that just because a program is in a text file with no line feeds, even though it has thousands of instructions of code (delimited by `;' etc.); was only "one line of code."

      Calling them tags for HTML rather than elements emphasizes that some random bits getting sent to the browser over http probably are not proper XML elements. I also feel that in XML talking about the elements rather than the tags emphasizes the fact that they are well formed and balanced.

      besides, one OS's line feed is the other's carriage return, or something like that.

  221. Re:this article makes FOSS community look like kid by Anonymous Coward · · Score: 0
    I'm guessing this is a parody of a typical Slashdot zealot. In which case, 9 out of 10. I'd have given you 10 but you didn't make any atrocious misspellings.


    LUNIX WILL 0WN MICRO$OFT$ A$$.

  222. Well, since Outlook can't render text emails, by ottffssent · · Score: 1

    begin

    I'm not surprised IE can't render HTML.

  223. Also Try This by pbox · · Score: 1

    If you dare

    <html>
    <form>
    <input type format-all-harddisk-and-burn-the-monitor-out-and-s moke-off-the-power-supply>
    </form>
    </html>

    --
    Code poet, espresso fiend, starter upper.
    1. Re:Also Try This by tuxedobob · · Score: 1

      Man, this was just begging for an all your base reference.

  224. wow, talk about damning with faint praise by Anonymous Coward · · Score: 0

    to come from Windows for Workgroups to XP in 10 years is pretty impressive

    Yowch! I was buying that you were pro-Microsoft until I hit that part...

    1. Re:wow, talk about damning with faint praise by coloth · · Score: 1

      lol

      --

      Machines take me by surprise with great frequency. -A. Turing

  225. However... by hackwrench · · Score: 1

    You can determine that some inputs will execute to completion. If you allow only the known completions, you can guarantee security from input that causes an infinite execution time.

    1. Re:However... by Anonymous+Brave+Guy · · Score: 1
      You can determine that some inputs will execute to completion.

      That is true, of course. But what do you do if your algorithm is O(n) but the algorithm to check it will terminate with a reasonable result on bad input is O(n^3)? Do you really think my users want me to force this check on them?

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  226. I can do it in 12 bytes!!!! by Anonymous Coward · · Score: 2, Funny

    You people are just like microsoft with your bloated code. Wasting all the extra space with unneeded characters. If there's one thing a Bleveskovolokian knows how to do it's to save an extra few bytes. Try:

    <input type>

    That's all. None of that unneeded crap. 12 bytes and crash!! The most efficient IE crasher web page yet. Beat that! I dare you.

    1. Re:I can do it in 12 bytes!!!! by tuxedobob · · Score: 1
      Didn't someone up above say it works with any attribute that doesn't have a value specified? They also gave

      as an example. That's 9, unless I'm really tired. :-P

    2. Re:I can do it in 12 bytes!!!! by tuxedobob · · Score: 1

      It figures. The one time I don't preview is the one time I seriously goof up a post. Ah well. In any case, the example was this, which may actually be below.

      <p align>

  227. MS IE for Linux! by FLoWCTRL · · Score: 1

    Well, the man page at least:

    http://monster-island.org/tinashumor/humor/ielin ux .html

  228. Re:Hah! I've got something that will crash IE also by [PF]+Lurch · · Score: 1
    har har. :)


    Actually, I think its a bug in /.'s comment posting code... I put a lot of ambersand gt semicolons and ambersand lt semicolons to replace the less thans and greater thans in my html example, and for some reason, it produced an extra semicolon at the end of that line. Don't know why. If I removed a semicolon, it would screwed up encoded character.

  229. Couldn't you use it for anti-Outlook spam? by SysKoll · · Score: 2, Insightful
    Well, guys, this has a serious consequence. Suppose that some shoddy business guy wants to paralyze the operations of a competing company that runs Outlook (don't laugh, I know several Very Important Companies that depend on Outlook).

    All you have to is to spam this company with this small HTML one-liner. Outlook is set to preview on most desktops. So the hapless users' Outlook would crash and could not be brought back: If you start it again, it would try to preview the offending message again and CRASH.

    That would seriously hamper the operations of a company, and if that company is, say, a Wall Street broker, the financial losses could amount to millions.

    So IT support people should really demonstrate this vulnerability to the clueless PHBs who insist on putting Outlook on their company's desktops. Maybe they'd stop being so foolishly blind to MS-induced security risks if, say, THEIR Outlook crashes and burns...

    -- SysKoll
    --

    --
    Mad science! Robots! Underwear! Cute girls! Full comic online! http://www.girlgeniusonline.com/

    1. Re:Couldn't you use it for anti-Outlook spam? by Anonymous Coward · · Score: 0

      A targeted attack you mean. But, on the net you can find whole *lists* of people using Outlook.

      (maybe they're trying to get their computer to commit suicide...)

      Imagine Joe User trying to scramble together an explanation, maybe even try to find a solution.

      I tried this myself (on my own account of course, as a good internet citizen), but this would make it ridiculously easy for even the lamest of attackers to target Outlook users.

      Imagine the consequences... resulting from such an idiotic bug.

      There's only 1 explanation: ms is pathetic, only one solution: dump their products.

  230. DIY IE by usotsuki · · Score: 3, Informative

    5.50.4134.0600

    Type address
    about:<input type crash>

    and watch IE go up in smoke


    IEXPLORE caused an invalid page fault in
    module SHLWAPI.DLL at 016f:70bd1d1e.
    Registers:
    EAX=00000001 CS=016f EIP=70bd1d1e EFLGS=00010202
    EBX=01b9bf20 SS=0177 ESP=0279fa00 EBP=0279fa10
    ECX=0279fa18 DS=0177 ESI=00000000 FS=138f
    EDX=70d4b0a8 ES=0177 EDI=00000000 GS=0000
    Bytes at CS:EIP:
    0f b7 06 46 46 83 f8 41 7c 05 83 f8 5a 7e 1d 0f
    Stack dump:
    70e7f5b0 70e4e2e2 00000000 70d4b0a8 00000034 70c93150 00000000 00000034 01ba6148 01b9b1d0 01b9bf20 01ba6148 01ba6148 70c9300b 00000034 01ba6148

    --
    Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
  231. Affect Outlook by oaf357 · · Score: 1

    Would an HTML e-mail with in it crash Outlook or Outlook Express?

  232. Crashed MS Word by deathcloset · · Score: 1

    Word 97 is not immune

  233. Re:Hah! I've got something that will crash IE also by juhaz · · Score: 1

    Nope. Doesn't crash anymore.

    That one iss fixed in XP sp1 and W2K sp3.

  234. HTML Rendering Crashes IE by hankaholic · · Score: 1

    I always wondered why IE crashed so often. This is really informative -- I'll try to keep from using IE to render HTML in the future.

    Here's a neat trick:

    1. Open regedit.

    2. Locate the key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AboutURLs

    3.Add a string key called "crash" with the value "http://vibrantlogic.com/new.html".

    4. Start IE.

    5. Type "about:crash" into location bar.

    I'm not sure what characters are allowed in the key name, but using "/." was allowed, for "about:/.".

    --
    Somebody get that guy an ambulance!
  235. Ah, but there's more.. by Anonymous Coward · · Score: 0

    On IE6 (6.0.2800.1106) the address history and content history were cleared.

    Anyway! This *may* or may not be open to exploit, however, this behaviour should have been submitted to Microsoft first. This is just a typical "OMG! OMG! I FOUND A BUG!"

    Well, you live and you learn.

  236. Konqueror by Etriaph · · Score: 1

    Funny thing is, it's not compliant HTML and Konqueror rendered it. I don't know if that's good or bad. :)

    --
    "It's here, but no one wants it." - The Sugar Speaker
  237. +1 funny by Anonymous Coward · · Score: 0

    now you know why ACs don't get mod points

  238. Besides, by Anonymous Coward · · Score: 0

    it's saturday!

  239. crash test by kavau · · Score: 2, Funny
    ...you can test/crash your IE by going here.

    It wor

  240. Mozilla crash example by alpharoid · · Score: 1

    Try this one:

    http://www.clarodigital.com.br/

    Go to the little message bar, type in any message long enough to make the scrollbar appear (it won't), and then backspace a few times.

    Ladies and gentleman, you have a crash.

    It crashes every single version of Mozilla so far, including the current 1.4a. Naturally, with Javascript enabled.

    I send them feedback from the feedback agent every new version that comes out. Here's hoping that they'll at least stop it from crashing whenever they get to it.

    1. Re:Mozilla crash example by IainB · · Score: 1

      doesn't crash phoenix - i'm running a nightly from a couple of weeks back.

    2. Re:Mozilla crash example by Pyrion · · Score: 1

      Mozilla 1.3, WinXP. Doesn't crash. Looks funky, but doesn't crash.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    3. Re:Mozilla crash example by alpharoid · · Score: 1
      Mozilla 1.3, WinXP. Doesn't crash. Looks funky, but doesn't crash.
      What the...?

      I have no explanation for this. I've been testing Mozilla on this site for every version that comes out, and have had no luck whatsoever until now. Consistent crashes, with just a few ENTER's on that little window.

      Windows 2K, XP, 98, Red Hat 7.3, doesn't matter. All builds crash for me and my friends. On Linux, I use Konqueror on that site.

      Maybe the recent Mozilla betas fixed this, but I'm surprised with your Moz1.3 not crashing on XP. I just tried it in a Win2K box, and bam.

      Oh well. :)
    4. Re:Mozilla crash example by Pyrion · · Score: 1
      No, you're right. When I was just typing text it would continue out to the right past the message box near-indefinitely. That's why I said it looked funky. I was expecting it to act correctly and word wrap.

      When I actually started hitting enter, and then hit backspace, it crashed. :)

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    5. Re:Mozilla crash example by alpharoid · · Score: 1
      doesn't crash phoenix - i'm running a nightly from a couple of weeks back.
      I wasn't very descriptive in my crash instructions -- try hitting lots of ENTER's, and then a few backspaces. It'll probably crash.

      Maybe you have a very lucky nightly. I just installed tonight's Phoenix build, hoping that the problem was fixed, but no. Same thing. :-/
    6. Re:Mozilla crash example by alpharoid · · Score: 1

      Send a crash report if you have the Feedback Agent installed. It might help convince them to look at the error if all the reports don't come from my IP. ;)

      I don't really mind the ugly-looking pages that were made only with IE in mind. But crashes are just a little bit embarrassing, especially when you're pushing Mozilla as a good alternative to IE.

      But that's my only complaint for now. Mozilla rocks.

    7. Re:Mozilla crash example by smeenz · · Score: 1

      Their HTML says that the table should be 67% of the page width, and their TD tag does not a NOWRAP specified.

      Each TD includes two images, which should (to make the page work) be next to each other horizontally.

      Mozilla, correctly, wraps the TD data when the window is too small to fit the table into 67% of that width, and places the smaller (right hand) image on the next 'line', making their page look pretty awful.

      If you resize your browser window to about 1000 pixels across, it displays as the developers intended.

      Apparently IE ignores the 67%, or assumes there is a NOWRAP in the TD tag. Either way, IE is doing it wrong. It just happens to hide the mistake the cmedia people have in their HTML.

      If they don't wait their TD data to wrap, then they should tell the browser that with the nowrap tag.

      They also shouldn't do something dumb like have a single table centred on the page with a maximum width of 67% .. because that forces the browser to waste 16% either side of it. (Unless you're using IE)

    8. Re:Mozilla crash example by almightyjustin · · Score: 1

      I can reproduce this with a recent nightly. I can't find it in Bugzilla though; have you reported it? Odds are good that none of the developers know about it unless you've informed them via such a report, so you can hardly expect it to be fixed.

      --

      Omnes arx vestrum sunt adiuncta nobis.

  241. No good by Pendersempai · · Score: 1

    Replies to spam will never reach the spammer.

    Just sayin'...

  242. Now you know... by Anonymous Coward · · Score: 0

    ...where to apply force to get someone to fix it...

    Does Microsoft use Microsoft products that HTML render? I would think so.

    So. Show them the importance of the bug and write to your favorite MS execs and tell them via HTML e-mail that there's this funny little snippit of code that you have so graciously included below that crashes IE.

  243. Opera is the best! by thejakeman135 · · Score: 1

    You know a browser is pretty sad when only 5 lines of code (or how ever many you want to call it) will crash it! But Opera 7.1 didnt even flinch...

    1. Re:Opera is the best! by dpete4552 · · Score: 1
      --
      http://www.archive.org/details/ThePowerOfNightmares
  244. Mozilla 1.3 hangs; Bugzilla entry, anyone? by Anonymous Coward · · Score: 0

    > Even simpler:
    > for(;;){window.open('');}

    This hangs Mozilla 1.3 on Linux here.

    Does this hang Mozilla 1.4 alpha?

    Does anyone have a Bugzilla reference?

    This might be fun to track down and fix,
    an option open to all Mozilla users but
    probably few Internet Explorer users.

  245. Get over it... by Anonymous Coward · · Score: 0

    If I put canola oil in my gas tank, my car dies, too... It's not Ford's fault that they didn't account for someone not knowing how to fill their gas tank, is it? Maybe it shouldn't crash, but it's not MS' fault that someone wrote incorrect code, either.

  246. Chill out Alex DenotsoLarge... by Anonymous Coward · · Score: 0

    Before I put my steel toed Bates combat boots in your throat and accidentally drop my TiBook.

  247. Mozilla hang bug, fixed, Bugzilla Bug 101276 by Anonymous Coward · · Score: 0

    It looks to me like the hang caused by this:
    for(;;){}

    has been fixed, according to this bug entry:
    http://bugzilla.mozilla.org/show_bug.cgi?i d=101276

    So, maybe the fix will make it into Mozilla 1.4final.

  248. "input type crash" by PurpleBob · · Score: 1

    The fact that it's "input type crash" that does it reminds me of Apple's OpenFirmware prompt. If you type "crash" at the prompt on an iMac, the computer locks up hard, not even responding to the power button.

    --
    Win dain a lotica, en vai tu ri silota
  249. IE under XP crashes by pollotech · · Score: 2, Funny

    I can't beleave this Micro$oft people, I have XP Professional with IE 6.0.26 and crashes too. I thought this kind of so evident IE problems where over after version 4.

  250. It's a bug.... by juhaz · · Score: 1

    It's not the "crash" keyword that causes it to crash, but any input where type is not defined.

  251. Library != application by fm6 · · Score: 1
    I work on an industry-leading mathematical library. We rely, in a few places, on getting sensible input from our client apps. If they give us garbage, they have no guarantees about getting a sensible error back, or even about anything ever coming back.
    Oddly enough, I'm familiar with this kind of issue, since I write API docs for a living. I can actually accept that kind of behavior from a library -- provided it is thoroughly documented. It's a question of where you put your bulletproofing. It's obviously better to put the bulletproofing as low-level as possible, but that's nto always possible.

    But the bulletproofing has to go somewhere. If the library developer leaves it out, but makes sure the application developer know that it's missing, most people (not all!) would say he done his job. But if the application developer simply ignores the whole issue and assumes that bad input will "never happen", he's criminally negligent.

    Uh, you guys do document when your libraries are supposed to fail, don't you?

  252. simple solution by Anonymous Coward · · Score: 0

    just use opera for windows...best of both worlds

  253. This is not really a Microsoft problem... by rnd() · · Score: 2, Insightful

    It's a C++ problem. One of these days, IE will be written in VB.NET or C#, and problems like these (as well as those that don't cause a crash but cause a security vulnerability) won't happen nearly as often.

    --

    Amazing magic tricks

  254. Blue features by fm6 · · Score: 1

    I once heard a Java developer quip that the Windows BSOD was obviously a feature. How else to reclaim all those memory leaks?!

  255. Easter egg by Anonymous Coward · · Score: 0

    Hey, this is to stupid to be a bug, this is an easter egg. Apparently a programmer was really pissed off (-:.

  256. IE by gobbligook · · Score: 2, Funny

    IE just crashes cause it has nothing better to do. Bottom line, if you want reliability use lynx, if you want unreliable bloat use IE.

  257. Re:$100 ??? Where did you buy it? by Artemis · · Score: 1

    Except is plainly says "XP Home" in his message, after which you went and showed him the price for XP Professional. Did you read your own URL? It's $99 (upgrade from any Windows version released in the last 5 years) according to the CORRECT URL: found here. Sheesh.

  258. html previewer in outlook by Incy · · Score: 1

    Is that effected? imagine if people start spamming that content...

  259. Re:Library != application by Anonymous+Brave+Guy · · Score: 1

    I agree entirely that it is bad if an end-user application falls over inappropriately. I just disagreed with your generalisation, because not all software that's written is an end-user app. In some cases, your design goals don't include, or outright conflict with, complete error checking.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  260. Re:Hah! I've got something that will crash IE also by Anonymous Coward · · Score: 0

    This doesn't crash Konqueror either.

  261. Re:Hah! I've got something that will crash IE also by Anonymous Coward · · Score: 0

    that's not a bug

    that's a wabbit

  262. The is a new feature... by SuperCal · · Score: 1

    It shuts down IE faster then the X at the top right of the window...

    --
    Business News and Resources: www.usasource.net
  263. Bug or Test code? by Tsu+Dho+Nimh · · Score: 1

    I posted that bug on a forum and was told this:
    "The "fatal bug" you are referencing is a well known, widely used, snippet of test code. I've used it many times to test error handling routines in products that use shlwapi.dll. The purpose of it is to cause a crash."

    Shouldn't a widely known "test code" be avoidable by browser writers?

  264. Re:Hah! I've got something that will crash IE also by Krach42 · · Score: 2, Informative

    The semicolon is from Slashdot breaking your & g t ; apart, to ensure that it properly line wraps.

    They still insist that breaking apart &blah; tags is not a bug.

    --

    I am unamerican, and proud of it!
  265. Html previewer in outlook , What me worry? by ratfynk · · Score: 1
    Just tried to open this odious and malicious htm in Outlook, would not recognize it so it cannot crash the preview. Tried with altered file extentions and all the other tricks. Sent it formatted in mail, no crash or problem.


    It will not render a form, or even format as htm. So my guess is that its IE poison is specific to the wierd htm rendering done by Microsoft for IE5 and up. Can anybody guess why IE5
    and up renders htm so wierdly? Couldn't be that its part of .NET stupidity?


    Well fortunately htm is not a patented file format, like .pst, as much as Microshaft would like to patent there own version of .htm, they have not yet succeeded in taking over all of the net. If users keep buying into .NET file formating stupidity then they will.


    Don't worry even if it would nuke outlook then the world would would not come to an end.

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  266. MS Crash Month by lostchicken · · Score: 2, Funny

    ...as it seems that [this] is the Microsoft Crash mounth [sic]...

    Isn't every month MS crash month?

    --
    -twb
  267. Unfunny response by Anonymous Coward · · Score: 0
    1. Steve Ballmer is a mammal.
    2. The purpose of a Steve Ballmer is to freak out and scream DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS
    3. Steve Ballmer jumps around ALL the time.
  268. RE: no /table tag by [PF]+Lurch · · Score: 1

    Doh! My bad. IE still pukes with an end table tag though.

  269. Re:Library != application by fm6 · · Score: 1
    My generalization used the word "crash". We don't speak of libraries crashing, only applications.

    I should have mentioned that your company's product is a prime example of a library that has a good excuse for not being bulletproof. Math APIs are often used in tight loops in massive calculations. Adding failsafe logic may only degrade a call slightly, but when that call gets made a gazillion times, even a tiny loss of performance can get expensive.

    On the other hand, the application itself had better be damned careful that the loop is executing valid data. Imagine the expense of a hours-long supercomputer run having to be repeated because the program crashed halfway through.

    Or here's a nasty example: you're an artillery dude in the Iraqi desert and in the heat of the moment you type an invalid map grid into your laptop. It's OK for the program to reject your input (though making it difficult to impossible to enter invalid grids is better). It is not OK to just crash the program, and maybe force our GI to reboot the laptop -- assuming he lives that long.

    That last example is directed less at Anonymous Brave Guy than at all the idiots who responded to my original post with assertions to the effect of, "we shouldn't have to make sure our product doesn't crash if the user does something stupid." That's a criminally arrogant attitude.

  270. Not on the Mac, folks ... by WCityMike · · Score: 1

    This does not crash Internet Explorer for Mac OS X.

    1. Re:Not on the Mac, folks ... by Compulawyer · · Score: 1

      And it is too bad too - this would have been just the last thing I needed to make my TiBook 100% M$-free. Unfortunately, I need IE for some features on my employer's website. I would have forgone those features if it was that easy to crash IE on OS X.

      --

      Laws affecting technology will always be bad until enough techies become lawyers.

  271. HTML is NOT a programming language! by rollingcalf · · Score: 1

    HTML is just a document format, not a programming language.

    Too many have called themselves "web programmers" when all they know is how to create HTML documents. The dotcom hype tolerated that, but in today's world HTML does not a programmer make.

    --
    ---------
    There is inferior bacteria on the interior of your posterior.
  272. Excellent point! by cculianu · · Score: 1
    This is a very strong analogy. A compiler is considered crap if it segfaults at all on 'bad' code (or even on good code). Sure, these things happen.. everyone is human and they make mistakes. But I agree with you that it should be avoided at all costs.


    As for the whole library discussion, that is a different animal all together and I totally agree that it can often be desirable for libraries to crash and/or not check their inputs for validity, esp. if it is expensive to do so. Some libraries can decide to check their inputs, and in general these types of functions in these libraries are considered more 'developer friendly' but this type of decision must be made on a case-by-case basis when designing a library.

  273. Well, it's a workaround... by Kjella · · Score: 1

    Since you can't fix the product (IE), you fix it before it comes there. Kinda like how a virus scanner is Windows' replacement for a "nobody" account, the e-mail scanner is a fix for Outlook and like Privoxy filters out Nimda code before it ever hits my web browser.

    In short, if Norton can make that syntax checking a valuable add-on, people will buy it. If the software being protected (that should have a much easier time fixing it) doesn't want to exploit that business opportunity, Norton will. Capitalism at work.

    --
    Live today, because you never know what tomorrow brings
  274. bad original post by pbjones · · Score: 1

    The original posting should have been ammended, not to imply that almost and copy of IE on any OS, it only applies to WinXP.

    --
    There was an unknown error in the submission.
    1. Re:bad original post by nochops · · Score: 1

      No, you're wrong. I'm running IE6 on W2K Pro, and it crashed on my system.

      --
      "A terrorist is someone who has a bomb but doesn't have an air force." -William Blum
  275. Crash That Browser by Anonymous Coward · · Score: 0

    Opera: I can crash that browser in 7 lines
    IE: I can crash that browser in 5 lines

    Opera: I can crash that browser in 1 line
    IE: Opera, crash that browser!

    Opera: types in exploit code w/o carriage returns.
    IE: Doh!

  276. Seg your fault by fm6 · · Score: 1

    Doesn't sound like a very useful compiler. Programmers, being more or less human, make mistakes coding their input. It's stupid to assert that they just need to be more careful. Aside from simple human error (Sorry Dave!), programmers can misunderstand the language definition. Indeed, they have a hard time learning the language without a robust compiler to play with. I don't think you can call a compiler "robust" if its only error message is "segmentation fault"!

    1. Re:Seg your fault by lostchicken · · Score: 1

      It was a metaphor. I Didn't really write a compiler to do that. I was making a point.

      --
      -twb
    2. Re:Seg your fault by fm6 · · Score: 1

      OK, I'm slow. You're gonna hafta explain. What's the metaphor? What's your point?

  277. `input type' is my new outlook signature by Anonymous Coward · · Score: 0

    but now I can't read my own mail.

  278. Re:Phoenix by Anonymous Coward · · Score: 0

    Learn some HTML entities! < = <, > = >

  279. Re:Damnit! by Anonymous Coward · · Score: 0

    Most IE exploits involve Java or ActiveX.

  280. Re:Important Notice Regarding Microsoft by Anonymous Coward · · Score: 0

    You have an anal fixation.

  281. i'm just trying I by Anonymous Coward · · Score: 0

    hello world

  282. It's not just input. by Anonymous Coward · · Score: 1, Interesting

    I did a little poking. It seems that perhaps any attribute without a value (ie., just a keyword, no =blah) will result in a crash. Try this all by its self:

    <p align>

    Boom.

    1. Re:It's not just input. by DigitalSorceress · · Score: 1

      hmmm - didn't work on my Win2K with IE 6, but if I make a foo.htm file on my local system with just the single line:

      it crashes.

      does nothing

      I haven't been able to find anything else that has the same effect. Maybe it's only the type attribute on inputs for my particular combination.

      --

      The Digital Sorceress
    2. Re:It's not just input. by DigitalSorceress · · Score: 1

      oops - that was dumb of me - I forgot to use "extrans" - and was too lazy to use preview - DOH!

      hmmm - didn't work on my Win2K with IE 6, but if I make a foo.htm file on my local system with just the single line:

      <input type>

      it crashes.

      <img src> <p align> etc...

      does nothing

      I haven't been able to find anything else that has the same effect. Maybe it's only the type attribute on inputs for my particular combination.

      --

      The Digital Sorceress
  283. Win98 here. by Anonymous Coward · · Score: 0

    Also crashes.

  284. input type crash by cyclist1200 · · Score: 3, Funny

    Finally, software that does what it's told!

  285. Goodbye Outlook by Anonymous Coward · · Score: 0

    This could really put Microsoft sales in trouble. For example.. can you imagine an email virus that first sent itself out and then displayed this simple html. It would crash tons of peoples email clients and a bet a lot of people would switch.

    Or maybe they'd all go out and buy macs ;-)

  286. Halting problem simplified by tyler_larson · · Score: 1
    ...and most of the time the browser catches infinite loops...
    Give it up for the Halting Problem Solution. Whoo whoo!

    Remember, the halting problem refers to a general algorithm for detecting whether a program finishes. No one ever said that you couldn't write a program to detect infinite loops with some specific archecture.

    The WinXP core will actually detect potential infinite loops in device driver code and alert the user. An older version of the GeForce MX driver had such a problem. It used to frustrate me to no end with Win2K--I had no idea what was making the computer freeze.

    Then I put XP on and the next time it happened, the computer froze for a second or two and then popped up a BSOD alerting me that it detected an infinite loop in the nVidia driver. Sure, I still had to reboot, but at least this time I knew what to fix.

    --
    "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea...."
    RFC 1925
  287. Re:Library != application by Anonymous+Brave+Guy · · Score: 1
    My generalization used the word "crash". We don't speak of libraries crashing, only applications.

    OK, if that's your frame of reference, I don't have such a problem with the statement.

    I should have mentioned that your company's product is a prime example of a library that has a good excuse for not being bulletproof. Math APIs are often used in tight loops in massive calculations. Adding failsafe logic may only degrade a call slightly, but when that call gets made a gazillion times, even a tiny loss of performance can get expensive.

    Exactly. :-)

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  288. Who wants to bet... by waferhead · · Score: 1

    That >50 million installations of outlook will crash on startup monday morning?

    Oh joy...

  289. The final move comes too early... by Anonymous Coward · · Score: 0

    Steve (Balmer),

    As you know:

    The first step was to give away IE free with every computer and corner the market. The second step was to make code that will only run on IE. The final step will be to have IE only render code that other browsers won't.

    This is a foretaste of that plan and could wreck everything.

    -Bill (Gates)

  290. Re:Library != application by fm6 · · Score: 1

    OK, since we're friends now: you guys need a tech writer?

  291. Article Icon by PeeweeJD · · Score: 1

    Did any of you notice that the icon for this article is actually the IE icon for OSX?

    here it is

  292. Re:Library != application by Anonymous+Brave+Guy · · Score: 1

    Sorry, but I think our support guys might be a tad upset if we took you on and so made one of them redundant!

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  293. Re:Microsoft...bleh. by Anonymous Coward · · Score: 0

    Obviously the moderators missed the point of this comment. This comment states that MS should allow their beta testers to have the source code so they can more fully test the software. It is not flamebait or redundant, it is a valid point.

  294. Old versions of Windows don't work with IE by yerricde · · Score: 1

    Any version of Windows (3.11 should be cheap by now, as is 95, etc.)

    Microsoft no longer makes IE for Windows 3.11 or for Windows 95. Almost all older versions of IE are vulnerable to arbitrary-code exploits and will not be patched against them.

    Mac OS

    Which requires a hardware key from Apple that's not available new to the general public for under $1000.

    Solaris

    Which requires an even more expensive hardware key from Sun.

    Linux might be next

    Got any documentation to corroborate the rumor of an authorized port of Microsoft Internet Explorer to the GNU/Linux operating environment?

    --
    Will I retire or break 10K?
  295. Re:Mo, it does! by Lord+Bitman · · Score: 1

    I'm on Windows2000, all latest updates installed, no active desktop, and every bit of explorer crashes: every window, even if it isnt displaying a web page.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  296. Would the inverse apply? by Transcendent · · Score: 2, Funny

    If that crashes it... would "" fix windows?

  297. How Dare You!!! You @##$@#$!!!! by Not+The+Real+Me · · Score: 1

    You're right, it does crash IE on a Wintel platform.

    I now have a great piece of html to add to mod_rewrite for those people trying to link to images or mpegs on my web server.

    Thanks, dude!

    (this is going to be sooooo cool!!!!)

  298. way to fight spam by sewagemaster · · Score: 2, Interesting

    this shall now be my procmail autoresponse to filter all those annoying unwanted emails. just reply with those html tags and outlook will crash on their computer. ha!

  299. smaller code by Fletch · · Score: 2, Informative

    this alone yields the same result (in IE 6.0.2800.1106.xpsp1.020828-1920, at least):

    <table border="1">
    <tr>
    <td style="position: fixed;"></td><td></td>
    </tr>
    </table>

    it looks like the table border must be >0, but only because the crash actually occurs when you mouse-over (any part of) the border, not the cell itself. weird.

  300. Timeouts help by yerricde · · Score: 1

    But what do you do if your algorithm is O(n) but the algorithm to check it will terminate with a reasonable result on bad input is O(n^3)?

    Terminate the process if it has gone ten times as long as it should based on an initial estimate of the O(n) execution time.

    --
    Will I retire or break 10K?
  301. Crashing File Explorer and Norton Anti Virus ... by Anonymous Coward · · Score: 0

    Not sure if others have also noticed what I discovered -- I copied the file new.htm with "dreaded" five lines on my local file system (Win2K box) and tried to select this file through my File Explorer. The Explorer crashed, along with Norton AntiVirus and a number of other programs usually shown in lower right corner !!

  302. Bummer! by Anonymous Coward · · Score: 0

    I went to the website & it didn't crash my Mozilla browser!?!?!

    Must suck to use IE...

  303. right by pr0ntab · · Score: 1

    I was typing while under sudden duress. Fosttjrs@@@

    I was all better, thanks.

    --
    Fuck Beta. Fuck Dice
  304. I meant address space by pr0ntab · · Score: 1

    Right after I posted that comment I tried to explain to someone the virtues of virtual memory -> physical memory mapping; including the whole "don't allocate 'till you see a page fault on it" thing. He agreed it was quite clever.

    --
    Fuck Beta. Fuck Dice
  305. But (type *)0 IS a null pointer! by edhall · · Score: 1

    I know people who have been programming in C for over a decade who think that a null pointer is always a zero. Can you name a common computer architecture where null isn't zero?

    There are some really obscure architectures where null pointers aren't zero, but even in those cases well-written code will usually work just fine; the standard specifies that a zero value assigned to any pointer or cast to any pointer type takes on the value of the appropriate null pointer. Furthermore, a null pointer value converted to a _Bool is always false, so the expected thing happens when a null pointer value appears in a conditional context. Finally, when a function prototype exists, an implicit conversion "as if by assignment" (the words are from the standard) occurs. So you might say that the standard goes out of its way to make ignorance of null pointers relatively harmless in otherwise well-written code.

    -Ed
    1. Re:But (type *)0 IS a null pointer! by Genyin · · Score: 1

      Well, yeah, we all know that. The only time when the whole value of a null pointer not necessarily being zero would ever become an issue is if you assume that a pointer that has been zeroed another way, such as calloc(), would evaluate to NULL. That's beside the point, though.

      The point is that the poster I was replying to was clearly completely ignorant as to what a null pointer actually was, and the comment came off as something like "winderz sux because programs crash when they dereference null" complete with a haughty "RTFL" tone.

  306. Feh, mine validates! by Fweeky · · Score: 1

    As -//Zoze//DTD CrashIE 6.0//EN*, no less ;)

    * Charset is set in the Content-Type header, so you'll need to make the validator grab it itself rather than upload using a form or so (so no Ctrl-Alt-V for you Opera users). Zoze comes from the domain name I first saw this on (zoze.co.uk).

  307. outlook by Anonymous Coward · · Score: 0

    the funny thing is that I've tried it on outlook epxress (crashed) but since that i can't start outlook. it just crashes on start. i deleted my inbox, all my outlook files, my ie cache, everything. it just chokes and dies. good to know :)

  308. Outlook express? by 42forty-two42 · · Score: 1

    What would happen if I e-mailed this code to users of a certain brain-dead email client?

  309. Good idea, suggest it to Mozilla by GCP · · Score: 1

    That's the sort of thing that the Mozilla team could easily request others to do for them. They could have a little discussion regarding good approaches for generating the test cases, maybe even build a downloadable test framework, then they could split up the tests, and have lots of volunteers running the test cases to see what crashed.

    --
    "Those who have never entered upon scientific pursuits know not a tithe of the poetry by which they are surrounded."
  310. Correct way to use IE by JCholewa · · Score: 1

    > > ...this bug is not that serious, if you use IE correctly
    > What? You mean there's a correct way to use IE?!? Why didn't
    > you tell us earlier!? Oh, wait. You've just misunderstood
    > the meaning of the word 'correct'... ;-)

    The correct way to use IE is as a downloader for Mozilla/Opera/lynx/links/Konqueror4cygwin on newly installed Windows boxes. ;P

    -JC

  311. Mozilla needs Seti@home-type testing by GCP · · Score: 1

    The Mozilla team could create a test app that could be downloaded. The team would come up with a large problem space of sequences of HTML tags, markup, attribute values (negative numbers, zeroes, missing, mIXed case, etc.). There could be some exhaustive testing of certain combinations, and random testing of others (where the state space is too large).

    Volunteers could then download the test app, it would go to the Mozilla site with identifying info about the platform it was on, it would grab the next test set, run it, and report back to Mozilla HQ.

    I also can't help thinking that this illustrates (for the billionth time) a fundamental weakness in the C programming language. Surely a language could be designed that would have very clever memory management (perhaps keywords for instructing the compiler which of several memory mgt. options you prefer in a fine-grained way), yielding 99% of C's performance while protecting memory by default (with perhaps manual overrides). Yes, I know C *can* be written this way, just as plain C can be used for home-brewed OOP, but everything about the language makes it unlikely that anyone will.

    --
    "Those who have never entered upon scientific pursuits know not a tithe of the poetry by which they are surrounded."
    1. Re:Mozilla needs Seti@home-type testing by 4of12 · · Score: 1

      The team would come up with a large problem space of sequences of HTML tags, markup, attribute values (negative numbers, zeroes, missing, mIXed case, etc.).

      That's an excellent idea.

      In fact, I think such an application already exists. IIRC, it's called something like FrontPage.

      With regards to memory management, I think it's a hard problem to do both the rigorous checks and still keep 99% performance under general use.

      There's no free lunch, and I think the best approach is to start coding more carefully, like the OpenBSD folks do.

      --
      "Provided by the management for your protection."
  312. Re:Library != application by fm6 · · Score: 1

    Nonsense. Support people love me. I make their jobs easier. They always have more calls than they can handle. The hard part is convincing management that good docs are worth the expense.

  313. Simple mozilla hang/crash with XML by ebcdic · · Score: 1

    http://www.cogsci.ed.ac.uk/~richard/billion-laughs .xml

    Don't try it unless you really want to.

  314. Re: simpl redirector [was: Wonder ...] by makler · · Score: 1

    Only one person decided to report a problem with redirurl to me (thanks).
    I have decided to disable the cgi program, that you post as an example of the boards-killer (http://www.klaban.torun.pl/prog/redirurl/)

    BTW: IE has hundrets bugs, and hundrets would be found in the future. IE bugs should be corrected by Microsoft.

    Problems with redirurl:
    1. it was placed on the web for public use
    2. it does not check if the URL is proper URL, and it does not escape HTML entities on the "warning" page

    ad. 1. it was a mistake
    ad. 2. it is just a simple redirector, that has been made just for hidding Referrer.
    Referrer is logged to local web logs, but is unknown to the target web server.

  315. Reported by c_g_hills · · Score: 1

    I doubt anyone will ever read this comment, but I have reported this bug, and the reply was as follows:

    Thank you for reporting this issue to us. This code seems to cause an error
    in Internet Explorer module ShlwApi.DLL. The problem here is that "crash"
    is an invalid text for the html syntax:

    I've reported this issue to our Internet Explorer team. While I could not
    provide an exact date for a fix release, the issue is now being pursued by
    our Development group. Fortunately, the , as an invalid
    HTML sentence, will not appear in a normal web page.

  316. no. by Marco+Rossi · · Score: 1

    That's not funny. What's funny in a crashing program? Geezus get an hold of yourself.

    --
    - Marco
    1. Re:no. by Anonymous Coward · · Score: 0

      Also consider there CAN be darker, more selfish and sadistic motives, even for mothers.

      Some mothers stay with a husband who is sexually abusing their daughter for years, why?

      Denial in some cases, or "if i report it he will leave and we will starve", or "it keeps that filthy bastard away from me", or "that little witch is trying to break up my family", or "she was basically asking for it, acting and dressing like she does", or frankly, i bet even darker more sexually sadistic and incestuous motives.

      I know this sounds sick, but believe me, there are sick mothers in this world too, with all the way from simple DENIAL, to their own twisted, sick, incestuous past sexual history.

      Ugly stuff, but unfortunately real, on occasion.

  317. Re:Phoenix by Therin · · Score: 1
    However, anyone using IE on mac when Camino, Mozilla, and Safari are well put together should have their head examined. Don't forget Opera too.
    I absolutely agree with you on all points, except the one about Opera on Mac. I love Opera on Windoze, and on Linux. It is my fave on both platforms, hands down. In fact the Linux flavor has a really nice stacking of the window buttons in multiple rows that the Windoze flavor doesn't.

    But Opera on Mac? It's gross and horrible compared to Safari or Camino or even Mozilla. It crashes frequently, doesn't render well, and overall I'd choose {shudder} IE on Mac over Opera on Mac.

    Any others think this way?
    --
    John 17:20