Le 2 juin 08 à 12:53, Kjetil S. Matheussen a écrit :
>
>> Hum.. what do you mean by disconnects"? There is no such "explicit"
>> kind of strategy implemented.
>>
>> What could happen in "asynchronous mode" (server not waiting for the
>> graph to finish) is that the server keeps activating the blocked
>> client, and the client may recover thus consume pending activations
>> until it is in sync again.
>>
>> Are you speaking of this kind of behaviour?
>
> Probably, I get lots of "JackAudioDriver::ProcessAsync Process error"
> when using too much cpu. It might not intentionally be a watchdog,
> but it does seem to work like one. :-)
In "asynchronous" mode, this message is printed when the server
detects a failing client. Because the server backend thread does not
wait for the graph to finish, it can just scan client running state at
the beginning of each cycle, and thus detect falling one. So in some
sense the server backend thread behaves like a "watchdog", but never
removing clients, just signaling something was wrong.
Stephane
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
