JACK clients hang on SHM read

[jackaudio]

JACK clients hang on SHM read

[karllinden]

Have done more research in this? Maybe you should try with the latest version of jack2 and a more recent kernel.

[mspanc]

That was long time ago so I write from my memory. But as far as I remember that was caused by buggy client connected to JACK daemon, most probably it was jack.plumber (that is buggy like hell) hanging on thread synchronization in callback. Or something like this.

The only question is how JACK daemon should treat such buggy clients? Do we assume that they should not deadlock on callback and not implement additional checks for e.g. performance reasons or should we drop them if that happens?

[x42]

Crippling the server (additional checks in the RT callback) to accommodate buggy clients is IMHO the wrong approach. Especially if you have access to the source-code of those clients and can fix those instead.

Even if you can come up with some logic how to determine and kill those clients, you'd still get a dropout whenever a client is kicked. (jack1 has a "zombify" features, but in the vast majority of cases it's a lot more trouble than it's worth)

just my 2 cents

[karllinden]

I agree with Robin. Closing. Reopen if necessary.