Hm great! Now every malware writer has a code that crashes flash. Let's hope Adobe releases the fix before there are exploits
Flash Crash (Warning, may crash your browser)
61–70 of 90 posts
Re: Flash Crash (Warning, may crash your browser)
#62Earlier quoted context omitted.
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.
Re: Flash Crash (Warning, may crash your browser)
#63Earlier quoted context omitted.
Anything, including corrupt files, that can crash it is relevant because it is also a security vulnerability.
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.
Re: Flash Crash (Warning, may crash your browser)
#64Didn't crash Gnash, but I'm not sure if it rendered "properly" either (I just saw a blue rectangle.)
Re: Flash Crash (Warning, may crash your browser)
#65Much praise to the Google Chrome team for handling this sort of thing gracefully.
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.
Re: Flash Crash (Warning, may crash your browser)
#66Earlier quoted context omitted.
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.
The Firefox nightly (3.7a1pre) also crashed.
Re: Flash Crash (Warning, may crash your browser)
#67Re: Flash Crash (Warning, may crash your browser)
#68Earlier quoted context omitted.
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.
Re: Flash Crash (Warning, may crash your browser)
#69Sorry, nothing happened. Firefox on OSX. Prolly the worst [anti-Flash] troll post so far.
Yay, the "works on my machine" syndrome ... love it :-)
Re: Flash Crash (Warning, may crash your browser)
#70Earlier quoted context omitted.
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.
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.
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?