Assertion '!in_worker(m)' failed at pulse/thread-mainloop.c:161, function pa_threaded_mainloop_stop(). Aborting.

[heftig]

Pidgin crashes with the following message:

Assertion '!in_worker(m)' failed at pulse/thread-mainloop.c:161, function pa_threaded_mainloop_stop(). Aborting.

Pidgin bug: http://developer.pidgin.im/ticket/10941
Backtrace: http://developer.pidgin.im/attachment/ticket/10941/ThreadStacktrace

Also see:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/458071
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/486896
https://bugzilla.novell.com/show_bug.cgi?id=606340
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553993
http://bugs.archlinux.org/20033

[vkrevs]

Same problem on openSUSE 11.2 for x86_64:

https://bugzilla.novell.com/show_bug.cgi?id=608633 https://bugzilla.novell.com/show_bug.cgi?id=606340

For me, this bug causes Banshee to crash at least once a day.

[coling]

The assertion would appear to be one to protect against invalid useage of the PA API (i.e. calling methods from an incorrect thread (e.g. unsafe thread handling).

This would seem to suggest one of two things:

1. A GST bug
2. A GST client (e.g. Pidgin) bug.

I don't know enough personally about either GST or Pidgin to comment about where the problem actually is, but I guess it's best to ask a GST expert to comment to see whether the Pidgin use of the GST API is following their thread guidelines, or whether it's just something that GST needs to wrap up in order to offer a thread-safe API to it's clients (e.g. buffer the request in question and execute it in the appropriate thread when possible).

[coling]

According to Sebastian Droge (a GST guy), this should be fixed in the latest gst-plugins-good. Can you confirm?

He said: 0.10.23 should have this fixed... relevant commits are e69ba0f94f475975cfa33d651a56fc1567c0238b 4a492f2c8a4dc3b00773ac222146344aea311a5a a8103facc59b9dde07ee95d026c3fd2323e278bb

I'll close this bug for now. If a real problem exists in PA itself or the above does not fix things for you, please comment back, otherwise other people reading this can assume this is fixed.

Cheers