In certain circumstances, the library is blocked on a select call.
The call stack is [1].
I think it occurs when the library tries to open a stream which is being closed
at the same time

That shouldn't be happening, because everything runs in a single thread. In each place in the code where a socket gets closed, "TaskScheduler::turnOffBackgroundReadHandling()" is supposed to also be called. This ensures that - once the code returns to the event loop afterwards - that socket number will no longer be among those accessed by "select()".

(I assume that you are using the latest version of the code, because there were changes made in January to fix a bug like this.)


, but I am not sure because I can't reproduce this easily.

If you can track this down some more, please let us know.
--

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

Reply via email to