Could it be that some crashes are the fault poor programming and not the Flash Player itself?
I can eat up 100% of your CPU with Python.
I can eat up 100% of your CPU with Python.
Things like bitmap manipulation and real-time filters (drop-shadow, glow etc), they are really easy to implement and designers love the effects that can be achieved and tend to design with them in mind (can't blame them really), but without optimization care and skill it will eat a CPU alive.
These effects can also be implemented without a single line of code, a lot of the time it is not even the developers at fault.
I worked agency level for a number of years before I lost the will to live and gave it up, I seen this kind of thing daily and the culture of getting it out there didn't help either, unless there was a really switched on PM or lead developer in charge who understood this optimization time was generally second class.
EDIT: it did not help that OSX was a second class citizen and Flash took a 15% hit in Firefox (windows) either.
That's why many will use Rentzsch' Click-to-Flash WebKit plug-in, to block all Flash permanently and play H.264 movies natively. github.com/rentzsch/clicktoflash
Here's another one, this time from Firefox for Maemo RC3:
> We’ve decided to disable plugin (not to be confused with add-ons, which are supported) support for this release. The Adobe Flash plugin used on many sites degraded the performance of the browser to the point where it didn’t meet our standards.
For Maemo, see earlier on Hacker News: http://news.ycombinator.com/item?id=1090855