#472: Segmentation fault when using module-jack ---------------------+------------------------------------------------------ Reporter: nwmatt | Owner: lennart Type: defect | Status: new Priority: normal | Milestone: Component: daemon | Severity: normal Resolution: | Keywords: ---------------------+------------------------------------------------------ Comment (by 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. -- Ticket URL: <http://www.pulseaudio.org/ticket/472#comment:4> PulseAudio <http://pulseaudio.org/> The PulseAudio Sound Server _______________________________________________ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets