Oops, I misread part of your earlier message. Now I think I understand what is
going wrong.
Yes, I think you are correct: There is potentially a problem if a
“RTSPClientSession” outlives a “RTSPClientConnection”, because the
“RTSPClientSession” can hold references to socket numbers that get re
> Explanation.
> - When RTSPServer::RTSPClientSession is created livenessTimeoutTask() is
> scheduled and it gets rescheduled while connection is on.
> - 60 seconds after connection is closed livenessTimeoutTask() is executed. It
> will delete clientSession, which will call reclaimStreamStates(),
Hi.
Noted this when using RTSP relay.
Use case (probably can be simplified):
- RTSP relay based on RTSPServer with RTP over TCP.
- Open connection (#1) and let it run. At this point relay connects to the
source stream and starts forwarding packets.
- Open another connection (#2) to the same stre
I’d still like to know exactly where/how/why the crash was happening, to make
sure that it’s not a problem with our code. (As always, I assume that you’re
using the latest version of the code.)
Also, you haven’t said anything about your “ServerMediaSubsession” object
(i.e., “stream->sms” in yo
Thanks for the advice, I haven't fixed the crash, but I've stopped it
from happening, I think.
In case anyone else hits this issue, I moved the call to
deleteServerMediaSession() to before the calls to close down the
streams, so my server shutdown code now looks like this:-
void CRTSPWrapper
