Segmentation fault when using module-jack

[nwmatt]

When I start Jackd in realtime and then pulseaudio in realtime, it all starts up correctly and gives me the proper connections. However, PA is very unstable. I can induce a segmentation fault by starting a video file in totem and then moving to a different location in the file.

[nwmatt]

PulseAudio Output

[nwmatt]

Jack Output

[nwmatt]

Pulseaudio configuration file

[coling]

Can you get a full backtrace please? either use ulimit -c unlimited prior to starting pulse and analyse the core file or run it in gdb (although that process is more complex due to the signal handling issues). Please make sure you have debugging symbols installed when you produce the backtrace.

For more information see http://fedoraproject.org/wiki/StackTraces and https://wiki.ubuntu.com/Backtrace

[nwmatt]

I was unable to produce a segfault while running gdb this morning. I was easily able to produce a:

W: module-jack-source.c: JACK error >zombified - calling shutdown handler< I: module-jack-sink.c: JACK thread shutting down.. I: module.c: Unloading "module-jack-sink" (index: #0).

which is functionally the same (no sound and frozen totem) by starting totem and the moving to a different location in the video. However, the totem process did not subsequently segfault.

I also tried to attach to a running instance of pulseaudio using "gdb -p PID" from a root command line. This stopped all audio immediately and was not very useful either.

Any suggestions? I will try again after work. Also, what would cause the zombified state?

[lennart]

Please try to provide a backtrace for this. Otherwise it is really hard to help you.

[nwmatt]

I tried again this weekend to produce a backtrace. I ran ulimit -c unlimited but no core file is produced when it does segfault. As before, if I run gdb, I do not get a segfault. Also, if I connect with the running process, it kills my session but does not produce a segfault. It appears that I am not able to help troubleshoot this case unless you know a way to force a core file.

In the meantime, I have come to the conclusion that module-jack-sink & module-jack-source are not currently stable enough for my use as

W: module-jack-source.c: JACK error >zombified - calling shutdown handler< I: module-jack-sink.c: JACK thread shutting down.. I: module.c: Unloading "module-jack-sink" (index: #0).

is as bad as a segfault for me. Therefore as the most workable solution, I just have qjackctl kill pulseaudio when I start and restart as jackd exits and do not try to use pulseaudio with Jackd.

[lennart]

There was some breakage in this area in JACK a while ago. I assume that this problem does not exist anymore. If it does feel free to reopen.