[Live-devel] live-devel Digest, Vol 92, Issue 23
Ralf Globisch
RGlobisch at csir.co.za
Thu Jun 30 03:17:27 PDT 2011
Hi Matt,
Interesting post about the CPU usage!
FYI, we recently upgraded our live555 version too and I also
noticed that my RTSP client application starts using up my processor
(only after experiencing network issues where the connection seems
to drop).
We are also still using the synchronous version of the client and stream over TCP.
I will revert our live555 version and confirm whether the issue still happens.
Regards,
Ralf
------------------------------
Message: 3
Date: Wed, 29 Jun 2011 10:38:29 -0700
From: Matt Schuckmannn <matt at schuckmannacres.com>
To: live-devel at ns.live555.com
Subject: [Live-devel] RTSPClient using the synchronous interface
spinning onthe processor
Message-ID: <4E0B6315.7080001 at schuckmannacres.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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.
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20110630/2a7b5a4f/attachment-0001.html>
More information about the live-devel
mailing list