[Bug 674626] New: [rtpsession] High CPU usage in rtcp thread when setting RR bandwidth = 0
bugzilla at gnome.org
Mon Apr 23 07:15:12 PDT 2012
GStreamer | gst-plugins-good | 0.10.31
Summary: [rtpsession] High CPU usage in rtcp thread when
setting RR bandwidth = 0
AssignedTo: gstreamer-bugs at lists.freedesktop.org
ReportedBy: daniela.muzzu at selexelsag.com
QAContact: gstreamer-bugs at lists.freedesktop.org
GNOME version: ---
If receiver report bandwidth is set to 0 according to SDP configuration (see
RFC 3556), it often happens that RTCP thread doesn't exit as expected, but
computes spurious next_rtcp_check_time values: this generally leads the
gst_clock_id_wait call to return immediately with GST_CLOCK_EARLY and the RTCP
thread to consume a lot of CPU time.
This issue happens only if the RR_bw=0 setting is performed after the RTCP
thread has been started, otherwise it's handled correctly: this behaviour has
been introduced with release 0.10.31, since in release 0.10.30 the RTCP thread
was never started until stream configuration completion (in gstrtspsrc.c
0.10.31 the state transition READY to PLAYING has been anticipated).
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs