(Adding Alan to Cc) On Fri, 26 Aug 2016 21:02:12 +0200, Samuel Thibault wrote: > > Samuel Thibault, on Sat 20 Aug 2016 14:12:05 +0200, wrote: > > I'd just like to check something: do we agree that libasound must be > > thread-safe by default (otherwise it breaks the application assumption > > that it's thread-safe)? If so, then there are thread-safety bugs: > > Ok, now with the discussion on the portaudio list starting at > > https://lists.columbia.edu/pipermail/portaudio/2016-August/000599.html > > it seems the issue was in portaudio, which was hit by the locking > behavior change. Good to hear that it's been addressed in portaudio side. But I still wonder in which code path the deadlock was triggered. Can anyone give the stack traces of deadlocked (multi-)threads? thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
