On Fri, May 9, 2008 03:24, Paul Davis wrote:
> Changes:
>
> * use poll+read, not just read, when waiting for clients to finish up
> non-process "event" handling
> * mark clients as Finished after their process callback has executed
> * remove clients that failed to respond to events
> * add new -r option to completely remove the JACK shm registry
> at startup (orthogonal to everything else, but in my codebase for months)
>
> I would commit this directly, but I'm trying to be cautious for once. It
> works much better for me now. Note that I believe there may be some
> locking issues still to address in the code (insufficient locking,
> that is, not deadlocks).
>
sorry to tell, but it still fails on the jack_test2.c crash tester (the
very same at stake on that last night in Cologne:)
fyi, this is just one simple client that, after a while, enters into an
endless loop and tests for jackd being able to detect and remove it from
the graph. what happens is that jackd gets severely stuck and
jack_watchdog kicks in and bang! everything is thrown to the floor
funny thing, and it might just be relevant to the case, is that this
meltdown behavior seems to be most evident when, and only when, the bad
client shares the graph with any other client. when left alone, everything
seems to work just fine. puzzled ;)
byee
--
rncbc aka Rui Nuno Capela
rncbc@...
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
