[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

** Tags added: lt-blocker lt-category-visible -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title: [pulsesink] abort at pthread_mutex_unlock(m-mutex)

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

This bug was fixed in the package glibc - 2.21-0ubuntu4 --- glibc (2.21-0ubuntu4) vivid; urgency=medium * debian/patches/arm/local-arm-futex.diff: Lie about the minimum kernel support for futex_atomic_cmpxchg_inatomic to restore the previous state and make pulsesink happier

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

** Changed in: glibc (Ubuntu) Status: Confirmed = Fix Committed ** Changed in: glibc (Ubuntu) Assignee: (unassigned) = Adam Conrad (adconrad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

** Branch linked: lp:ubuntu/vivid-proposed/glibc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0'

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

So this issue is a combination of the following patches: https://sourceware.org/git/?p=glibc.git;a=commit;h=47c5adebd2c864a098c3af66e61e1147dc3cf0b4 https://sourceware.org/git/?p=glibc.git;a=commit;h=03d41216fe09fc71a2750946af8fe2892bf4feb5 Basically the main problem is that

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

SMP support for futex_atomic_cmpxchg_inatomic was added in 2.6.38, but it required !CPU_USE_DOMAINS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title:

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

The mutex in question is the one used by pulse's mainloop, which gets used by pa_threaded_mainloop_lock, pa_threaded_mainloop_unlock and pa_threaded_mainloop_wait. As the pulseaudio calls are all asynchronous, gst (pulsesink element) calls pa_threaded_mainloop_wait right after calling

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

It seems the issue only happens when at least 2 threads are waiting for the wait condition (that gets triggered by pa_threaded_mainloop_signal). When I'm unable to make it to crash, it always shows only one thread waiting the signal. So my current theory is that there might be issues when calling

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glibc (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.