Hello Ross!
One more thing. Make sure that you're using a recent version
of the "H264VideoFileServerMediaSubsession" code here.
This was the code that was modified in a recent revision of the code
to fix a bug that was similar to the problem that you're seeing.
Do You mean this fix?
2011.06.14:
- Fixed a race condition in "H264VideoFileServerMediaSubsession" and
"MPEG4VideoFileServerMediaSubsession" that could have been
triggered when two separate clients tried to stream the same file
concurrently. (Thanks to Bruno Abreu for reporting this.)
I have written my child class of OnDemandServerMediaSubsession using
2011.03.14 version of liveMedia (without this fix).
Now I have included this fix to my class code and update liveMedia to
2011.08.13 but the bug I described still arises.
The fix 2011.06.14 refers to TWO clients connecting to one stream (so there
was TWO RTSPClientSession objects waiting for SDP of one stream).
The bug I described refers to ONE client connecting to one stream which
source have long initialization period.
The reason of the bug (delete RTSPClientSession object in nested doEventLoop
call while this object is still used in outer doEventLoop call) is not
affected by this fix.
Best regards,
Vadim Kosarev
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
