Flash Crash (Warning, may crash your browser)(flashcrash.dempsky.org)
flashcrash.dempsky.org
Flash Crash (Warning, may crash your browser)
http://flashcrash.dempsky.org/
28 comments
Player team update here, 6pm Saturday Pacific:
http://blogs.adobe.com/emmy/archives/2010/02/flash_bug_repor...
Much praise to the Google Chrome team for handling this sort of thing gracefully.
And much praise to the Opera team for just not crashing in the first place. I can zoom in the blue square, move around, etc. and the page is still fine after a minute or so leaving it open.
This is excellent. But I wish I could see an error/warning message a la Chrome.
However, i did notice a perceptible bump in memory usage via the System Monitor panel applet. The POC probably exploits a known Memory-allocation bug.
[Currently running Opera 10.10/i686 Linux] Edited: Grammar
However, i did notice a perceptible bump in memory usage via the System Monitor panel applet. The POC probably exploits a known Memory-allocation bug.
[Currently running Opera 10.10/i686 Linux] Edited: Grammar
Can anyone enlighten me on this? I noticed the same thing:
* Viewing this page in Firefox 3.6 on Windows caused Flash to crash, taking the browser down with it.
* Viewing it in Chrome on the same machine caused the Flash plugin subprocess to crash, resulting in an error message in Chrome.
* However, no crash occurred in Opera. This despite the fact that 32-bit Opera on Windows does not appear to use isolated subprocesses for running NSAPI plugins.
So what's going on here? Does Opera use some sort of in-process isolation to protect the browser from its plugins? Or is there perhaps some quirk of running in the Opera environment that caused this Flash crash not to be triggered like it was in Firefox and Chrome?
* Viewing this page in Firefox 3.6 on Windows caused Flash to crash, taking the browser down with it.
* Viewing it in Chrome on the same machine caused the Flash plugin subprocess to crash, resulting in an error message in Chrome.
* However, no crash occurred in Opera. This despite the fact that 32-bit Opera on Windows does not appear to use isolated subprocesses for running NSAPI plugins.
So what's going on here? Does Opera use some sort of in-process isolation to protect the browser from its plugins? Or is there perhaps some quirk of running in the Opera environment that caused this Flash crash not to be triggered like it was in Firefox and Chrome?
Adobe Flash on Opera/Linux has always been quirky , crashy and all-round unreliable for me in the past. So, I use Opera as my pure-HTML+javascript browser, with ALL plugins, sound, animation, and Java plugins turned off in Global preferences.
Going off-topic [Opera praise]: These settings instantly turn Opera into the most stable and shockingly scalable 'Research and reference' browser I've used. I only use Firefox3.5.x solely for web-dev, Google Apps, heavy-JS Web 2.0 apps, and Flash-enabled sites of course (with Flashblock as first-line-defence).
Going off-topic [Opera praise]: These settings instantly turn Opera into the most stable and shockingly scalable 'Research and reference' browser I've used. I only use Firefox3.5.x solely for web-dev, Google Apps, heavy-JS Web 2.0 apps, and Flash-enabled sites of course (with Flashblock as first-line-defence).
Chrome doesn't crash either, just the plugin in a separate process.
Same with the latest versions of Safari, except it takes down all instances of Flash, even those in other pages, which is obviously inferior.
Same with the latest versions of Safari, except it takes down all instances of Flash, even those in other pages, which is obviously inferior.
Konqueror stays open too!
Yeah, it also looks like Safari's recent improvements in terms of plugins that they introduced in Snow Leopard have successfully prevented this problem from taking down the whole browser.
How recent? 4.0.4 crashed for me.
NOTE: I generally browse with ClickToFlash active in Safari. That of course prevented the crash (until I clicked).
With Safari 4.0.4 (ClickToFlash turned off) the browser was fine but the Flash plug-in died, and Safari informed me:
> Flash Player (Safari Intenet plug-in) quit unexpectedly. > This report will be sent to Apple automatically.
PS: 10.6.2, FWIW
With Safari 4.0.4 (ClickToFlash turned off) the browser was fine but the Flash plug-in died, and Safari informed me:
> Flash Player (Safari Intenet plug-in) quit unexpectedly. > This report will be sent to Apple automatically.
PS: 10.6.2, FWIW
You need to have at least Snow Leopard, I believe. Apple recently moved plugins to separate processes, which prevents the entire browser from crashing. Flash will crash, but it won't take down the whole browser.
Except IIRC this wasn't about security or stability; it was because they went 64-bit on everything and needed a way to have the 64-bit apps and 32-bit plugins interact sanely.
[deleted]
The Firefox nightly (3.7a1pre) also crashed.
It handles it less gracefully than I would have assumed. If you are running flash in multiple Chrome windows, this will corrupt ALL of them, instead of just the one visiting the page linked above. Wasnt one of Chrome's huge selling features the idea of memory independence?
Memory independence + plugin that isn't designed to run multiple processes = plugin that can only run in one process. Imagine if Flash, forced into running twice, tried to read and write from the same cookie / any other kind of data, without any concurrency tools of any kind.
Chrome has to run Flash how Flash wants to be run, because doing otherwise could cause massive problems with any plugin. This is part of why it took so long for them to make Chrome, resolving the memory independence desires with the needs of plugins requires giving some things up. It was either roughly all plugins in existence, or allow the same process to interact with multiple tabs / windows.
Chrome has to run Flash how Flash wants to be run, because doing otherwise could cause massive problems with any plugin. This is part of why it took so long for them to make Chrome, resolving the memory independence desires with the needs of plugins requires giving some things up. It was either roughly all plugins in existence, or allow the same process to interact with multiple tabs / windows.
This sounds a bit fishy to me. Of course Flash can be run from multiple processes simultaneously since it naturally runs inside of multiple browsers simultaneously, and I assume Chrome has some internal (socket based?) IPC that they're using anyway...
Flash on multiple browsers has completely separate cookie and data stores. Flash on a single browser has a single cookie and data store. Without introducing a complex forking/merging infrastructure for that data (which only Adobe would be able to create anyway) you're stuck with a single process for the plugin for all of the tabs in a single browser.
Flash actually has one cookie & data store. It exists between browsers.
You can see your flash cookies at this website:
http://www.macromedia.com/support/documentation/en/flashplay...
You'll notice that they are the same no matter what browser you use.
You can see your flash cookies at this website:
http://www.macromedia.com/support/documentation/en/flashplay...
You'll notice that they are the same no matter what browser you use.
This page crashed flash for me! Wow!
Part of the difficulty is that this problem applies to all plugins. Flash may be able to handle it just fine, in which case it could just be a poor plugin, but what about any other plugin out there?
Heck, Firefox uses a lock-file in your profile to prevent multiple instances from running. What's to stop a plugin from requiring such a file, writing / reading it frequently, and having no error handling because it's only designed to run singly? Ultimately, you either harden the separations to run multiple instances of it, breaking many in the process and possibly damaging data irrecoverably, or you just let the plugin decide and have backwards compatibility, which is hugely important for a browser.
Heck, Firefox uses a lock-file in your profile to prevent multiple instances from running. What's to stop a plugin from requiring such a file, writing / reading it frequently, and having no error handling because it's only designed to run singly? Ultimately, you either harden the separations to run multiple instances of it, breaking many in the process and possibly damaging data irrecoverably, or you just let the plugin decide and have backwards compatibility, which is hugely important for a browser.
Interestingly enough the "libflashplugin.so" bar popped up on Gmail for me the last time that all my Flash instances crashed. I never realized that GMail used Flash. (The bar only seemed to pop up on tabs that were using Flash, not all tabs had the warning at the top)
Gmail uses flash for the file upload progress bar when adding an attachment. Will HTML5 allow developers to add this feature?
Flash is also used to make that popping sound when you get a gtalk message.
It is? Why?
Don't know about HTML5 (I can hope), but it can be accomplished with JS + hidden iframe for uploading. I think it requires querying the server for the progress, but I could be wrong there.
Flash is to blame for that one.
Within fifteen seconds of Flash Crash crashing my Flash, my laptop's fan stopped for the first time today. I think I might just uninstall flash.
Put a warning in the title, please. Blind linking to a browser crashing demo is not cool.
Edit: Thanks.
Edit: Thanks.
ClickToFlash for the win.
Firefox 3.6 on Ubuntu x64, Flash v10.0.32.18ubuntu1, seems to survive. Chrome survives too, unsurprisingly. Come to think of it, doesn't Firefox have plugin crash safety in place now?
Midori does insta-crash though.
Midori does insta-crash though.
ff 3.5 on a similar setup crashes. 3.6 was when ff made itself less vulnerable to this sort of thing, following webkit's and chrome's ideas on isolating plugins.
Are you sure that's in 3.6? My 3.6 build doesn't have the "dom.ipc.plugins.enabled" key in about:config.
I'm pretty sure it'll be landing in 3.7. Here's the tracking bug that shows what's left to fix on it: https://bugzilla.mozilla.org/show_bug.cgi?id=539055
I'm pretty sure it'll be landing in 3.7. Here's the tracking bug that shows what's left to fix on it: https://bugzilla.mozilla.org/show_bug.cgi?id=539055
IE8 does not crash. Chrome handles the crash and shows a message. Firefox dies.
ClickToFlash for Safari/Webkit on Mac is one of the best add-ons I've found.
http://clicktoflash.com/ http://github.com/rentzsch/clicktoflash
http://clicktoflash.com/ http://github.com/rentzsch/clicktoflash
FlashBlock for Firefox. https://addons.mozilla.org/en-US/firefox/addon/433
Yes, but oddly it seems to circumvent Safari's protective spawning of Flash to a separate process when it does load. When I clicked the browser-crashing Flash app, it actually crashed Safari, and Activity Monitor never picks up the separate Flash process anymore.
Are you sure you're not running Safari in 32-bit mode? The separation is only set up when Safari is running in 64-bit. That setup worked fine for me; clicking the plugin loaded it, and a few seconds later it crashed and turned into the block without crashing Safari.
Using the webkit nightlies and regular Safari on Snow Leopard with ClickToFlash installed, I just shows a blue ? box and a crash report.
Weird, it doesn't crash on me here. I'm using Opera 10.10 browser on OS X 10.6.2
Steps to get Adobe to fix this bug:
1) Create a flash ad with this bug. Set to go off randomly 2) Put ad in a low-cost adwords campaign
1) Create a flash ad with this bug. Set to go off randomly 2) Put ad in a low-cost adwords campaign
Yup, crash on mine. WebKit nightly on OSX, everything up-to-date. Thankfully, it just crashes the plugin (though it holds up the browser for a bit), everything keeps working.
I guess the Adobe CTO missed this one...
This isn't new either. Matthew posted this over a year ago.
How do we downvote for linking to the actual crash with no warning.
It's always nice to see bugs are addressed quickly . . . which Is why I'm not really surprised, Adobe products have always had a clunky feel to me and Flash was genuinely a product destined for them.
Opera and Internet Explorer 8 display the page without crashing.
Hm great! Now every malware writer has a code that crashes flash. Let's hope Adobe releases the fix before there are exploits
Didn't crash Gnash, but I'm not sure if it rendered "properly" either (I just saw a blue rectangle.)
On Snow Leopard and Safari, the browser doesn't crash, but the Flash player crashes.
It's crashing for me with Snow Leopard 10.5.2 on a Core Duo (32 bit obviously) and Safari
Version: 4.0.4 (6531.21.10)
Build Info: WebBrowser-65312110~2
Code Type: X86 (Native)
Parent Process: launchd [157]
PlugIn Path: /Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player PlugIn Identifier: com.macromedia.Flash Player.plugin PlugIn Version: 10.0.42 (1.0.4f348472)
Date/Time: 2010-02-05 22:06:52.926 -0800 OS Version: Mac OS X 10.6.2 (10C540)
PlugIn Path: /Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player PlugIn Identifier: com.macromedia.Flash Player.plugin PlugIn Version: 10.0.42 (1.0.4f348472)
Date/Time: 2010-02-05 22:06:52.926 -0800 OS Version: Mac OS X 10.6.2 (10C540)
Yay for writing software in C. It crashes really fast!
Seems fine with flash 10.1 beta 2, Safari on Mac.
Mine didn't crash... ????
You know this whole Flash debacle is a real shame because Flash, at least the concept of Flash, is really a great idea with lots of potential.
Flash allows people to create wonderful things (just visit newgrounds.com) but Adobe's lack of commitment to improving it is dragging it down and could be its unfortunate downfall.
Flash allows people to create wonderful things (just visit newgrounds.com) but Adobe's lack of commitment to improving it is dragging it down and could be its unfortunate downfall.
No it's not. No it doesn't.
Flash is a terrible concept just like Java Applets were a terrible concept, and its only potential is annoying advertisements, slow splash pages that keep away return visitors, and browser crashes.
Flash is a terrible concept just like Java Applets were a terrible concept, and its only potential is annoying advertisements, slow splash pages that keep away return visitors, and browser crashes.
Why are Flash's bugs only a problem when when Steve Jobs mentions it? Is Flash really a problem or are we just overcome by Job's reality distortion field?
Flash does stuff that HTML cannot currently do. In this respect hackers should thank Adobe as Flash helped move applications off the desktop and onto the web. When HTML5 has matured, the gaps in HTML will be filled and unless Flash has something new to offer, it will be time for give it a heartfelt goodbye.
Adobe's saving grace is that it released FABridge - you can use Flash for things its good at Ajax for everything else. Then when HTML5 has matured you wont have to rewrite everything.
Flash does stuff that HTML cannot currently do. In this respect hackers should thank Adobe as Flash helped move applications off the desktop and onto the web. When HTML5 has matured, the gaps in HTML will be filled and unless Flash has something new to offer, it will be time for give it a heartfelt goodbye.
Adobe's saving grace is that it released FABridge - you can use Flash for things its good at Ajax for everything else. Then when HTML5 has matured you wont have to rewrite everything.
The issue is that Flash seems to be getting worst. And we see a light at the end of the tunnel (new features being added to browsers to do what we use Flash for).
So the building of frustration with Flash over time, a general dislike of closed systems, and a light at the end of the tunnel has combined into the general "fuck you flash" feelings that seem to have sprang up over the last few months in developers. Which is awesome! As the web needs to outgrow proprietary plugins.
So the building of frustration with Flash over time, a general dislike of closed systems, and a light at the end of the tunnel has combined into the general "fuck you flash" feelings that seem to have sprang up over the last few months in developers. Which is awesome! As the web needs to outgrow proprietary plugins.
"As the web needs to outgrow proprietary plugins."
I agree. What bothers me is all this "frustration" showing only after Steve Jobs mentions it. I highly doubt his reason for bashing Adobe is due to his love for open web standards --
What I dont get is how hackers can side with Apple against Adobe given the iPhone App store mess... The model of the App store is against everything the open web stands for -- I think hackers should be more upset with Apple than Adobe.
I agree. What bothers me is all this "frustration" showing only after Steve Jobs mentions it. I highly doubt his reason for bashing Adobe is due to his love for open web standards --
What I dont get is how hackers can side with Apple against Adobe given the iPhone App store mess... The model of the App store is against everything the open web stands for -- I think hackers should be more upset with Apple than Adobe.
Well, it works.
Sorry, nothing happened. Firefox on OSX.
Prolly the worst [anti-Flash] troll post so far.
Prolly the worst [anti-Flash] troll post so far.
Crashed for me on Firefox 3.6 OS X 10.6. Google Chrome 4.0 gracefully handled it through (only the Flash Plugin crashed)
Yay, the "works on my machine" syndrome ... love it :-)
[Updated for technical clarity, rather than refuting bias]
Reading the original article, the issues seems to be with AVM1, the portion of the Flash Player dedicated to legacy Flash (v8 and older). Flash Player was updated in 2006 to include AVM2 and that's been Adobe's focus ever since.
Translation for HTML people: it's like pointing out IE6 bugs that still show up in IE7.
This is nothing more than an out of date flame post.
(Downvoters: have you actually looked at the nature of the bug?)
Reading the original article, the issues seems to be with AVM1, the portion of the Flash Player dedicated to legacy Flash (v8 and older). Flash Player was updated in 2006 to include AVM2 and that's been Adobe's focus ever since.
Translation for HTML people: it's like pointing out IE6 bugs that still show up in IE7.
This is nothing more than an out of date flame post.
(Downvoters: have you actually looked at the nature of the bug?)
Adobe's CTO claimed that they don't ship versions of Flash that are known to crash. The bug this triggers is more than a year old and the only versions it does not crash is the most recent _beta_ version of Flash. The post merely points out the deception in Lynch's claims.
I updated my post to explain why the bug is irrelevant.
Anything, including corrupt files, that can crash it is relevant because it is also a security vulnerability.
[deleted]
By my understanding, there will always be lots of ways to intentionally crash a browser. I know very little about crash-related security vulnerabilities, so I didn't see this threat as relevant.
I think you might be thinking of locking up the browers, rather then crashing it. You can easily create a javascript program that will run a loop that will make your browser non-reactive.
But this is very different the plugin actually crashes. The security issues comes in to play because when the plugin crashes it is doing something it wasn't designed to do. So (in theory) someone malicious could take this crash and make the flash player do something specific it wasn't designed to do like run some code outside of it's sandbox. Which obviously would be a very big deal.
This is different then the lock up/DoS case where a product is doing what it is meant to do, but will just take a very long time (maybe forever) to finish it.
But this is very different the plugin actually crashes. The security issues comes in to play because when the plugin crashes it is doing something it wasn't designed to do. So (in theory) someone malicious could take this crash and make the flash player do something specific it wasn't designed to do like run some code outside of it's sandbox. Which obviously would be a very big deal.
This is different then the lock up/DoS case where a product is doing what it is meant to do, but will just take a very long time (maybe forever) to finish it.
Considering it's still occurring in the most recent release of Flash Player 10, I'd say it's nothing like pointing out IE6 bugs at all.
If they had actually fixed that bug in the Flash plugin and people were using older versions, then you might have a point.
If they had actually fixed that bug in the Flash plugin and people were using older versions, then you might have a point.
The bug has to do with loading 5+ year old Flash 7/8 swfs.
A better analogy would be he's making a stink about a Carbon bug for obsolete OS 8/9 apps. Carbon still ships with OSX and serves the same purpose as AVM1 in Flash Player: basic (but not perfect) backwards-compatibility for legacy code.
A better analogy would be he's making a stink about a Carbon bug for obsolete OS 8/9 apps. Carbon still ships with OSX and serves the same purpose as AVM1 in Flash Player: basic (but not perfect) backwards-compatibility for legacy code.
I'm surprised that more priority hasn't been put into fixing it though. A bug that crashes the browser out in the wild for a year and a half? Someone malicious could do some pretty obnoxious things with it.
Incidentally this use case isn't completely unheard of. There is still a lot of AS2 content out there that companies haven't bothered to migrate to AS3 yet (for whatever reason).
Incidentally this use case isn't completely unheard of. There is still a lot of AS2 content out there that companies haven't bothered to migrate to AS3 yet (for whatever reason).
If you don't have the resources for fixing old known bugs, then you should remove backwards compatibility, especially since bugs are caused by buffers/stack overflows / segmentation faults ... which could lead to unauthorized code executed on your machine. How else do you think botnets are made?
$ lynx --dump http://flashcrash.dempsky.org/
References