[Bug 747614] New: gst-rts-server: uninitialized clock rate causes critical warning

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=747614

            Bug ID: 747614
           Summary: gst-rts-server: uninitialized clock rate causes
                    critical warning
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: All
            Status: NEW
          Severity: minor
          Priority: Normal
         Component: gst-rtsp-server
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: zzoon.ko at samsung.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

During gst_rtsp_stream_transport_get_rtpinfo, clock rate is not initialized.
If this can't get valid clock rate in gst_rtsp_stream_get_rtpinfo, it causes
Gstreamer-CRITICAL message like below.

0:00:02.486835007 18340  0x9693a00 DEBUG     rtspmediatransport
rtsp-stream-transport.c:349:gst_rtsp_stream_transport_get_rtpinfo: RTP time
2787330729, seq 13871, rate 3077981536, running-time 0:00:00.000000000

(lt-test-mp4:18340): GStreamer-CRITICAL **: _gst_util_uint64_scale_int:
assertion `num >= 0' failed
0:00:02.486903950 18340  0x9693a00 DEBUG     rtspmediatransport
rtsp-stream-transport.c:364:gst_rtsp_stream_transport_get_rtpinfo: RTP time
2787330728, for start-time 0:00:00.000000000


clock rate's tye is guint, but as an argument of _gst_util_uint64_scale_int, it
is type-casted to gint. During this, clock rate turns negative value.

It should be initialized.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.