> No, that happens only if the call to “isSSM()” returned True - i.e., only if > the stream is ‘source-specific multicast’ - which is definitely not the case > here (you’re streaming via unicast). So that’s a ‘red herring’. > > isSSM() is definitely returning true.
Then something is badly fucked up in your system - it’s apparently stomping on memory when it shouldn’t - because the only time “isSSM()” is ever supposed to return True is if you’re using ‘source-specific multicast’, by creating “Groupsock” objects with a ‘source filter address’ parameter. That doesn’t happen anywhere within our RTSP server code. > (In any case, we’ve probably pretty much reached the limit in how much > assistance I can provide ‘for free’ on this mailing list. If your company is > interested in having me consult further on your project, then please let me > know (via separate email).) > > That's fair enough. Once I have the scheduler blocking issue resolved, I'll > reach out. We do need some help and we certainly have budget for it. We’re definitely at that point now. 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
