Flash is a piece of absolute shit

[Dominus Atheos]

I found a website guaranteed to make flash crash and depending on your browser take the browser with it.

Just to repeat, this will crash your browser.
Spoiler

http://flashcrash.dempsky.org/

Firefox, IE6, IE7, and Safari all crash; Chrome and IE8 don't. God I hope and pray for the day when I can finally uninstall this awful glob of fuckslop.

[Singular Intellect]

Left your link open in another tab while replying here.

Looks like it doesn't crash my Internet Explorer or interfere with my browsing whatsoever.

I wasn't expecting it too either...go figure.

[Dominus Atheos]

Left your link open in another tab while replying here.

Looks like it doesn't crash my Internet Explorer or interfere with my browsing whatsoever.

I wasn't expecting it too either...go figure.

Did you miss the part where I said IE8 wasn't affected?

[Ryan Thunder]

I found a website guaranteed to make flash crash and depending on your browser take the browser with it.

Just to repeat, this will crash your browser.
Spoiler

http://flashcrash.dempsky.org/

Firefox, IE6, IE7, and Safari all crash; Chrome and IE8 don't. God I hope and pray for the day when I can finally uninstall this awful glob of fuckslop.

For some reason I'm reminded of the guy at my office who thought QA was "break the software using obscure, highly technical things that nobody will ever do."

[Dave]

I didn't have any problem with Firefox 3.6 on Windows 7 64-bit. (No clue what my flash player is.)







i

[Phantasee]

It's been open for a bit and I didn't have a problem. Firefox 3.0.18, WinXP.

Sorry DA.

[Dominus Atheos]

WTF? It crashes my Firefox 3.5.8 on Win 7 x64 every time I click on it.

[adam_grif]

Crashes my FF (whatever the current version is) on my 32 bit AMD Athalon 3500+ ( ) running XP.

[Bounty]

Win7 x64, FF 3.6, no crash.

[Phantasee]

Oh hey, it's not the bigger blue flash box like the site claims, it's the tiny little one to the right. I have to turn flash objects on individually because I'm using Flashblock.

[adam_grif]

Oh hey, it's not the bigger blue flash box like the site claims, it's the tiny little one to the right. I have to turn flash objects on individually because I'm using Flashblock.

Yeah I had to do the same to get it to crash.

[Twigler]

Win 7 64bit, FF 3.5.8 - no crash. I left it open for about 10 minutes just in case it's a slow one, but nada.
Odd, since that's the same setup as Dominus Atheos...

[Dave]

Ok, testing on a university computer:
Firefox 3.0.10 -- crashes
IE 7.0.5730.13 -- stable, seems functional and everything.
Windows XP SP 3, 32-bit

Flash version here is 10,0,22,87
(to see your flash version, go here: http://www.adobe.com/software/flash/about/)

[General Zod]

Without knowing exactly how this flash was made, it's hardly a testament that flash is shit in and of itself. There's a number of other scripts out there that will crash your browser too.

[General Zod]

LOL

Adobe CTO Kevin Lynch claims that the company's ubiquitous Flash plug-in doesn't ship with any known crash bugs. One can only assume that he has never used the software. As Adobe representatives exhibit an increasingly dismissive attitude about Flash's technical deficiencies, the browser vendors have stepped up to address the problems and are finding ways to insulate their users from Flash's poor security and lack of stability.

Several mainstream browsers isolate Flash and other plug-ins in separate processes in order to prevent an unstable plug-in from crashing the entire browser. Mozilla is preparing to introduce a similar feature in the next version of Firefox. A developer preview that was recently made available to users offers an early look at the new plugin crash protection.

It's part of a broader Mozilla project called Electrolysis that seeks to eventually bring full support for multiprocess browsing to Firefox. Electrolysis will make it possible for a browser crash to be isolated to a tab or group of tabs rather than affecting the entire browser. Similar functionality is already available in Internet Explorer and Chrome. Although Mozilla has already taken major steps towards implementing holistic multiprocess browsing, the plugin isolation is the only part that will land in the next release.

As we explained last year when we first covered Electrolysis, Mozilla has adopted parts of Chrome's interprocess-communication (IPC) implementation. In the latest developer preview build, it is used to facilitate interaction between the isolated plugins and the rest of the browser. Mozilla created its own protocol, called IPDL, that is used to define the messages that are passed between the processes through the IPC layer. For more details about IPDL, you can refer to the introductory tutorial that has been published at the Mozilla developer website.

In the developer preview, a plug-in that crashes will be replaced with a warning message. It will automatically transmit a crash report to Mozilla. You can resurrect the crashed plug-in by reloading the page. In the current implementation, each plug-in operates in its own process that runs separately from the rest of the browser. For example, when you load up pages that have Flash and Silverlight content, Flash and Silverlight will each have their own process. Individual plug-in instances are not isolated from each other.

There's more in the link. But still, lol.

[Singular Intellect]

Did you miss the part where I said IE8 wasn't affected?

My bad, I actually didn't catch that part. Point against skimming through the OP apparently.

Honestly though, it kinda ruins your point if the problem is merely old and obselete programs being affected, don't you think?

[Marcus Aurelius]

Crash here. Probably depends more on Flash than browser version.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100214 Ubuntu/9.10 (karmic) Firefox/3.5.8
Flash: You have version 10,0,45,2 installed

[Executor32]

I waited 5 minutes with no crash. Win7 x64, FF3.6, Flash 10.1b3.

[Dominus Atheos]

I waited 5 minutes with no crash. Win7 x64, FF3.6, Flash 10.1b3.

I'm sure that's because you're using the beta of the next version. The webpage says the author reported the bug in 2008, so they had to fix it eventually.

[Phantasee]

So then what's the problem?

[Marcus Aurelius]

So then what's the problem?

It's beta, that's the problem. Even if the beta fixes this problem, it may introduce others. In fact that is to be expected or otherwise it would not be beta anymore.