Comment 70 for bug 192888

Juergen: yes, the real fix should be inside the Adobe's blob [according to bug tricket on pulseaudio it's some kind of race condition inside plugin itself where pulseaudio only triggers the problem and not cause) :) However using nspluginwrapper has more advantages as well: if every plugins would use separated environments (eg security policies can be applied more easly to them), it can be good for security and also helps load multiple cores/CPUs because running as a separate process. It also helps firefox not to be so slow to react when a plugin inside the firefox process is too resource hungry. So, even this fix does not cure the real problem, it's the best besides the fix of the plugin itself (only adobe can do it), and also it can be good for crash protection in future similar bugs. And has got other advantages too, I've described (security, better usage of multiple CPUs/cores). So using nspluginwrapper is a good thing or at least some kind of similar separation should be developed for firefox to allow to separate plugins from the core borwser itself better. Sure, this was IMHO and AFAIK :)