Browser crashers warm to data fuzzing

The Register ^ | 13 April 2006 | Robert Lemos

[ShadowAce]

[Red Badger]

FIREFOX RU-HOIUH&#)(*$)(PJNLKJPOI)(#&-LES!..........oops! fuzzy data..........

[ShadowAce]

LOL!

[Petronski]

Hilarious little Firefox ad, lol.

[ShadowAce]

UNfortunately, those are in Quicktime format, and I am running under Linux--no QT plugin is available for Firefox under Linux. :(

[ShadowAce]

LOL! Saw it (DL'ed it and played it in Xine)

SHUT UP!!!

[Petronski]

I don't know if it is worth the effort, but apparently there might be a realtime plugin available for linux/mozilla. Or maybe not. I've never used the stuff at the link, but I sure did google it up right quick.

[ShadowAce]

Yeah--I've seen that. The plugin for Quicktime requires Codeweavers' Crossover Plugin, which I don't have.

That's OK, though. I can just "wget" them and view them in Xine.

[glorgau]

Hah! Flaws in ASN.1. Do like I did, just write your own parser/encoder. ;-) Actually, I only handled a subset of BER. It was a great learning experience.

[Michael Barnes]

You ever mess with Mplayer?

[zeugma]

Bump for later

[ShadowAce]

yeah--a little. Wazzup?

[antiRepublicrat]

Oh, come on, you don't even need mangled code to crash IE.

You can crash IE with a static web page that validates perfectly at the W3C for CSS and XHTML. Don't believe me? Skeptics are welcome to try it.

This page has been up for about a year and a half now.

[postaldave]

when you run into stuff like that look at the source code.

http://media.revver.com/broadcast/19542/video.mov

here is the file if you want to watch it on a linux system.
mplayer picked it up fine.

[Petronski]

I guess I'm not the only one who hunts for links in the sourcecode. ;O)

[Petronski]

I just realized you needed QT and I linked you to Real.


WTF was I thinking? Not very helpful.

[rzeznikj at stout]

It is a good clip ;)

I don't know why, but I was able to access it with the mozilla plugin for MPlayer.

Maybe I just got lucky...

[stylin_geek]

I took a look at the code behind the page, it took me less than a minute to find what caused the problem and fix it. And, I'm not a web designer, in any real sense of the word.

Before you ask, I use Firefox 95% of the time, I did it just to see how difficult it would be.

[antiRepublicrat]

I took a look at the code behind the page, it took me less than a minute to find what caused the problem and fix it.

But that's the point. The page is 100% valid CSS and XHMTL. There was nothing to fix, only somthing to change so that a browser doesn't crash. BTW, did your fix result in valid CSS and XHTML?