[Live-devel] RTSPClient using the synchronous interface spinning on the processor

[Matt Schuckmannn]

Yes it works fine.

Thanks,
Matt S.


On 6/29/2011 11:17 PM, Ross Finlayson wrote:
>> The first time BasicTaskScheduler::SingeStep is called the fReadSet, 
>> fWriteSet, and fExceptionSet are all empty and select() returns an 
>> error (WSAINVAL) and the code starting on line 86 of 
>> BasicTaskScheduler.cpp (did I mention I'm on Windows) gets invoked to 
>> create a dummySocket so that the error doesn't occur again. However, 
>> the problem is from then on select() will always return immediately 
>> indicating that dummySocket is ready for writing and that's why my 
>> client is spinning at 100 percent on the CPU.
>
> Try commenting out lines 91 and 92 of 
> "BasicUsageEnvironment/BasicTaskScheduler.cpp" - i.e., don't add 
> "dummySocket" to "fWriteSet" or "fExceptionSet".  I'm hoping that this 
> won't trigger the Windows bug that forced me to add "dummySocket" in 
> the first place - i.e., I'm hoping that I need to add "dummySocket" 
> only to "fReadSet".
>
> Please let me know if this works for you.