All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mznyfn@0pointer.de>
To: pulseaudio-discuss@mail.0pointer.de, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Asynchronous notification in	ALSA - I/O Plugin - Pulseaudio
Date: Thu, 22 May 2008 15:59:51 +0200	[thread overview]
Message-ID: <20080522135951.GA16685@tango.0pointer.de> (raw)
In-Reply-To: <g13rdf$6os$1@ger.gmane.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

  reply	other threads:[~2008-05-22 13:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8280850.2291211189691895.JavaMail.root@intra>
2008-05-19  9:38 ` Asynchronous notification in ALSA - I/O Plugin - Pulseaudio Juha Erkkilä
2008-05-19 17:53   ` Pacho Ramos
2008-05-20 11:07   ` Takashi Iwai
2008-05-21  6:46     ` Juha Erkkilä
2008-05-21 10:47       ` Takashi Iwai
2008-05-21 22:29         ` [alsa-devel] " Lennart Poettering
2008-05-22 13:11           ` Colin Guthrie
2008-05-22 13:59             ` Lennart Poettering [this message]
2008-05-23  9:07               ` Colin Guthrie
2008-05-21 22:24   ` Lennart Poettering

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080522135951.GA16685@tango.0pointer.de \
    --to=mznyfn@0pointer.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=pulseaudio-discuss@mail.0pointer.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.