[pulseaudio-discuss] Issue in libpulse crash for calc_next_timeout

Dhananjay Joshi dhananjayingroup at gmail.com
Wed Aug 17 13:03:22 UTC 2016


ohh my bad.. thanks for the reply.
using the locking APIS fixed the issue.

On Tue, Aug 16, 2016 at 6:29 PM, Tanu Kaskinen <tanuk at iki.fi> wrote:

> On Tue, 2016-08-16 at 18:20 +0530, Dhananjay Joshi wrote:
> > Hi Arun,
> >
> > Thanks for the reply.
> > we tried updating to pulseaudio-9.0 and simulated the test case in loop .
> >
> > as we are getting the same crash , and the frequency of the  crash is
> also
> > same as that of pulseaudio-6.0.
> >
> > stack trace for this is
> >
> > > #0  __GI_raise (sig=sig at entry=6) at
> > ../nptl/sysdeps/unix/sysv/linux/raise.c:57
> > 57    ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or
> directory.
> > (gdb) bt
> > > #0  __GI_raise (sig=sig at entry=6) at
> > ../nptl/sysdeps/unix/sysv/linux/raise.c:57
> > #1  0xb6bf7690 in __GI_abort () at abort.c:89
> > #2  0xb527d4f4 in calc_next_timeout (m=<optimized out>) at
> > /u02/yoctobms/build/info3-low/tmp-eglibc/work/cortexa7hf-
> vfp-neon-kpit-linux-gnueabi/pulseaudio/9.0-r0/pulseaudio-
> 9.0/src/pulse/mainloop.c:719
>
> This looks like a concurrency bug in the application. You seem to be
> using the threaded mainloop. My guess is that you're accessing libpulse
> objects from a non-mainloop thread without locking the mainloop first.
>
> --
> Tanu
> _______________________________________________
> pulseaudio-discuss mailing list
> pulseaudio-discuss at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20160817/446684f4/attachment.html>


More information about the pulseaudio-discuss mailing list