|
|
|
I'd like to add my experience with this bug, also confirming it.
I'm using the current version (9.0.124) of the flash player. My OS is Gentoo Linux x86 (Testing), with all current updates installed. Pulseaudio version is 0.9.10. As reported by others around the internet, crashes occur when leaving a page which contains flash content. Crashes happen much more frequently when a FLV video is played within the plugin, thus highly affecting YouTube and other video sites. I tried to use strace to produce a trace file which may give a clue on when the crash happens, but while dumping the trace it's almost impossible to trigger a crash. As Firefox and the flash plugin run very slowly while tracing, this could probably be a timing issue. It's interesting that no-one has mentioned libflashsupport yet.
The pulseaudio bug #264 only happens via the libflashsupport API. There are however also issues with using the pulseaudio alsa plugin to redirect the standard flashplugin alsa output to a PA server. The most concise summary of the problems come from Lennart Pottering (PA developer) from the PA mailing list: Using ALSA as backend for Flash: The current version of Flash relies on snd_async_add_pcm_handler() to be available in ALSA in all cases. This is ugly (especially from a plugin, since it relies on unix signals), and broken (since they don't properly handle the signal handler context) and cannot be properly supported in the PA backend for libasound (unless we'd resort to some exceptionally ugly hacks, which would have no chances to get upstream to alsa-plugins). Using libflashsupport as backend for Flash: There's a race condition in the way Flash tears down libflashsupport backends. It's something that cannot be worked around from our implementation of libflashsupport. See the explanation down on http://pulseaudio.org/ticket/267 for more information. So I guess this could be considered as two separate bugs. I didn't find any bugs in here that mention libflashsupport. so I don't thing there are duplicates yet. The crashes still occur with Flash 10 beta (10.0 b218). I do hope someone is working on this issue. It would be insane to leave this issue unresolved in the final version.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
It really needs to be fixed ASAP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!