From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lennart Poettering Subject: Re: [alsa-devel] Asynchronous notification in ALSA - I/O Plugin - Pulseaudio Date: Thu, 22 May 2008 15:59:51 +0200 Message-ID: <20080522135951.GA16685@tango.0pointer.de> References: <18027403.3701211352364970.JavaMail.root@intra> <20080521222936.GB12214@tango.0pointer.de> Reply-To: General PulseAudio Discussion Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: pulseaudio-discuss-bounces@mail.0pointer.de Errors-To: pulseaudio-discuss-bounces@mail.0pointer.de To: pulseaudio-discuss@mail.0pointer.de, alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Thu, 22.05.08 14:11, Colin Guthrie (gmane@colin.guthr.ie) wrote: > > That freeze is an unfixable race condition that Flash has when > > shutting down audio. > > > > See the explanation down on http://pulseaudio.org/ticket/267 > > I thought the whole point was that by adding async code to ioplug, the > libflashsupport stuff wasn't needed and flash could just use it's native > alsa support + alsa's pulse plugin.... or am I missing the point here? The destruction dead lock issue is present both in libflashsupport and the native ALSA backend. It's just that it is almost never triggered if a hw device is used. Adobe released the sources of libflashsupport where you can actually check this. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4