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

Matt Schuckmannn matt at schuckmannacres.com
Wed Jun 29 10:38:29 PDT 2011


I just updated my code to use the latest Live555 code and I imeadiately 
noticed that my RTSP client application is spinning on the processor and 
taking up 100% of the processor it's running on. I tried running 
OpenRTSP against the same server and I don't the problem. The main 
difference between OpenRTSP and my client is my client is still using 
the synchronous interface and OpenRTSP isn't.
The application seems to be spinning in the 
taskScheduler().doEventLoop(), and or SingleStep() methods. It's almost 
as if Select() is always returning immediately or something like that.
Did I miss something that I should have changed with my client?

I did noticed that with the new synchronous interface I am nesting calls 
to doEventLoop().
i.e. my app cals doEventLoop() at start up and then each time I I need 
to send a SET_PARAMETER command the synchronous interfaces calls 
doEventLoop() again, Could this be the problem?

I'll continue to debug and figure it out, but I appreciate any suggestions.

Matt S.




More information about the live-devel mailing list