Ticket #501 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Bad handling of JACK errors

Reported by: patrakov@… Owned by: lennart
Milestone: Component: module-jack-*
Keywords: Cc:

Description

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.

Change History

Changed 3 years ago by patrakov@…

  • summary changed from Bad handlink of JACK errors to Bad handling of JACK errors

Changed 3 years ago by lennart

  • status changed from new to closed
  • resolution set to fixed

That's brokeness in JACK which I think got fixed since then. I problem persists with current PA and current JACK feel free to reopen.

Note: See TracTickets for help on using tickets.