> And this is still the flow-graph that has lock/unlock() in it?   From the 
> report of very-high
>   rescheduling interrupts, I wonder if there's a subtle bug in the Gnu Radio 
> block
>   scheduler around lock()/unlock() that causes horrible thrashing.

It's pretty easy to get wedged forever if you call lock and unlock a lot in 
conjunction with connect and disconnect.  Sooner or later, you'll hit a race 
and things will get stuck.

I have a simple reproduction case if anyone is interested.  It'll hang reliably 
after a few dozen iterations.


_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to