Prevent jack-applications from hanging when one of the connected applications crashes
Bug #308002 reported by
Moe
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| jack-audio-connection-kit (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Would it be possible for you to integrate some sort of exception handling or security check into the flow of audio data in jack to prevent jack-related applications from hanging when one of it's (connected) applications is closed or crashes. For example if I connect my mplayer to an equalizer app and the eq to the system speakers, i cannot close the equalizer without mplayer hangs. Wouldn't it be nice if jack simply reroutes the data to some null device until a new application is conntected to it?
| Changed in jack-audio-connection-kit: | |
| importance: | Undecided → Wishlist |
| Changed in jack-audio-connection-kit (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| raboof (arnouten) wrote | #1 |
To post a comment you must log in.
If an application closes, it should be removed from the JACK connection graph, connections will be removed but previously-
In your example, the mplayer data should indeed be ignored until a new application is connected - this is how JACK should work right now.
Do you see anything interesting in the JACK 'Messages'? ('Messages' window if you use qjackctl, else look at the console)