#501: Bad handlink of JACK errors --------------------------------+------------------------------------------- Reporter: patra...@gmail.com | Owner: lennart Type: defect | Status: new Priority: normal | Milestone: Component: module-jack-* | Severity: normal Keywords: | --------------------------------+------------------------------------------- In setup described in #500, after 30 minutes of work, bad errors appear:
{{{ E: asyncq.c: q overrun, queuing locally #(repeated a lot of times) E: asyncq.c: q overrun, queuing locally I: memblock.c: Pool full I: memblock.c: Pool full E: asyncq.c: q overrun, queuing locally I: memblock.c: Pool full I: memblock.c: Pool full E: asyncq.c: q overrun, queuing locally I: memblock.c: Pool full I: memblock.c: Pool full E: asyncq.c: q overrun, queuing locally I: memblock.c: Pool full I: memblock.c: Pool full E: asyncq.c: q overrun, queuing locally I: memblock.c: Pool full I: memblock.c: Pool full <snip a lot of repetitions> W: module-jack-source.c: JACK error >cannot read server event (Success)< W: module-jack-source.c: JACK error >cannot read server event (Success)< W: module-jack-source.c: JACK error >cannot read server event (Success)< W: module-jack-source.c: JACK error >cannot read server event (Success)< <snip> }}} and pulseaudio dies (sometimes with a segfault). It looks like jackd dies first for some unknown reason. This should kill pulseaudio (or at least the sink) instantly, without this huge log. -- Ticket URL: <http://pulseaudio.org/ticket/501> 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