uninterruptible process with 100% CPU usage

[robinst]

In this bug report, various users describe that Totem (and other applications using pulseaudio) becomes uninterruptible (cannot kill it even with -9) and uses 100% CPU. I also had this a few times and only a reboot solves it.

The cause for this may be in pulseaudio, this is the last output before it happens:

E: thread-posix.c: Assertion 'pthread_setspecific(t->key, userdata) == 0' failed at pulsecore/thread-posix.c:194, function pa_tls_set(). Aborting.

See also the attached stacktrace, which is originally from this bug report.

[robinst]

stacktrace pa_tls_set

[robinst]

I used the wrong link, the bug report where users report this is Totem is 'uninterruptible'.

[lennart]

This looks a lot like some memory corruption issue.

Any chance you can reproduce this and get me valgrind output?

Also, I'd like to know the exact return value of pthread_setspecific(). Any chance you can get me this?

[robinst]

I haven't experienced this problem for some time, and now I'm on Ubuntu Intrepid which probably uses a newer version of pulseaudio, so maybe it's already fixed.

Tried starting Totem with valgrind but it runs too slow to be usable. Do you know if it is possible to use valgrind only for pulseaudio?

[lennart]

This was a problem with dlunloading modules if I remember. Which has been fixed a while back in PA. Closing.