Thank you for the post, gpulier.
I would just like to say i've found, "You often end up with multiple Flash Players enabled in chrome://plugins which can conflict" very true.
A lot of 'page(s) unresponsive'... The crash on websites i've found today - also on prior occasions - signalled a new Shockwave Flash Plugin, (ver: 184.108.40.206) had been automatically updated and dually enabled with my prefered older one.
Well, it's been updated, so i did enabled the new 220.127.116.11 on its own to test out - I do hope it's one that is stable! - but on Chrome you have to check 'chrome://plugins' quite frequently of late...
I believe it's fine if you have multiple copies enabled in chrome, this is the default for all installs. From what I can tell, Chrome uses the top one and ignores the rest.
I also thought that was the case but after very systematic tests on over 5 different computers I can conclude with a high degree of certainty that having multiple Flash Plugins enabled results in many issues (some of which I mentioned in my first post). So maybe it is a Chrome bug that is not completely ignoring the rest.
I'm currently working on a project where Stage3D comes into play and after reading, that some problems with the flash player in Google Chrome exist, I gave it a try and updated Chrome. Wow, after the update has finished I noticed a dramatic decrease in performance!
Here are my findings:
Having all player-versions marked as aktiv in chrome://plugins
Chrome is using 18.104.22.168
I see in the Away3D stats that software rendering is used. Performance is terrible! 8-10 Frames
Chrome is using 11,3,300,271
I see in the Away3D stats that hardware acceleration is used (DirectX9). Performance is great! 58-60 Frames
Chrome uses 11,4,402,265
As with 11,3,300,271 great performance.
I fear not a lot of people are changing manually their used flash plugin in Chrome and they will blame Flash for melting down their computers.
I'll follow up with your report with our internal Chrome team. In the meantime, would you mind opening a new bug report on this over at the Chromium bug database?
I've just now tested on both Windows and Linux Chrome version 22.0.1229.79
this flash :
after a while (about 2 minutes) the following error message will appear:
Shockwave Flash has crashed...
No other browser and platfrom configuration can reproduce this crash, with this flash animation.