Ticket #244 (closed bug: invalid)

Opened 11 years ago

Last modified 9 years ago

FFADO dies after JACK client timeout

Reported by: das Assigned to:
Priority: major Milestone:
Component: Version: FFADO SVN (2.0 branch)
Keywords: Cc:
The device the bug applies to: Echo Audiofire 4


Every time a JACK client exits uncleanly, FFADO/JACK goes down with it. This is caused for example by a client exiting without calling jack_client_deactive(), segfaulting, etc.

I'm running the latest versions of JACK (0.118.1) and FFADO (2.0 branch). The same thing happens with FFADO trunk. A complete log of a short JACK session is attached.


ffado-client-segfault.log (236.7 kB) - added by das on 12/03/09 09:39:51.
JACK log while a client segfaults at startup
ffado-diag.log (7.2 kB) - added by das on 12/03/09 09:40:44.

Change History

12/03/09 09:39:51 changed by das

  • attachment ffado-client-segfault.log added.

JACK log while a client segfaults at startup

12/03/09 09:40:44 changed by das

  • attachment ffado-diag.log added.

12/04/09 12:56:42 changed by arnonym

  • milestone deleted.

Hm, using jackd0.116.1 from the ubuntu-packages and ffado from 2.0-branch it doesn't crash jack when I kill jack-clients with signals -9, -11 or -15...

03/27/12 06:53:27 changed by adi

  • status changed from new to closed.
  • resolution set to invalid.

jackd separates its clients from the backend, in this case FFADO, so this is not an FFADO bug.