<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><div class="">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’.</div></div></div></blockquote><div class=""><br class=""></div><div class="">isSSM() is definitely returning true. </div></div></div></div></div></blockquote><div><br class=""></div>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.</div><div><br class=""></div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><div class="">(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).)</div></div></div></blockquote><div class=""><br class=""></div><div class="">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.</div></div></div></div></div></blockquote><br class=""></div><div>We’re definitely at that point now.</div><br class=""><div apple-content-edited="true" class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Ross Finlayson<br class="">Live Networks, Inc.<br class=""><a href="http://www.live555.com/" class="">http://www.live555.com/</a></span></span>
</div>
<br class=""></body></html>