[Bug 771830] There is no time out in idle connection RTSP server
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Mon Nov 21 22:35:14 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=771830
Tim-Philipp Müller <t.i.m at zen.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #340428|none |needs-work
status| |
--- Comment #19 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Comment on attachment 340428
--> https://bugzilla.gnome.org/attachment.cgi?id=340428
Yet Another Updated Patch vol 1
Thanks, but I get lots of leaks reported in 'make check-valgrind', e.g.
gst/rtspserver.valgrind
==2668== 544 (208 direct, 336 indirect) bytes in 2 blocks are definitely lost
in loss record 5,594 of 5,684
==2668== at 0x4C2CBC5: calloc (vg_replace_malloc.c:711)
==2668== by 0x67CBE60: g_malloc0 (gmem.c:124)
==2668== by 0x67C41FD: g_source_new (gmain.c:915)
==2668== by 0x67C740E: g_timeout_source_new_seconds (gmain.c:4734)
==2668== by 0x4E6AB0E: gst_rtsp_client_attach (rtsp-client.c:4346)
==2668== by 0x4E6B28B: manage_client (rtsp-server.c:1057)
==2668== by 0x4E6B5FC: gst_rtsp_server_io_func (rtsp-server.c:1191)
==2668== by 0x59B7290: socket_source_dispatch (gsocket.c:3543)
==2668== by 0x67C66A9: g_main_dispatch (gmain.c:3203)
==2668== by 0x67C66A9: g_main_context_dispatch (gmain.c:3856)
==2668== by 0x67C6A5F: g_main_context_iterate.isra.29 (gmain.c:3929)
==2668== by 0x67C6B0B: g_main_context_iteration (gmain.c:3990)
==2668== by 0x10C8E8: iterate (rtspserver.c:58)
==2668== by 0x10D3EB: do_request_full (rtspserver.c:350)
==2668== by 0x10F1D2: do_request (rtspserver.c:421)
==2668== by 0x10F1D2: do_describe.constprop.4 (rtspserver.c:448)
==2668== by 0x10F3E4: do_test_play_full.constprop.2 (rtspserver.c:1030)
==2668== by 0x10FD6D: thread_func (rtspserver.c:1638)
==2668== by 0x67EE344: g_thread_proxy (gthread.c:784)
==2668== by 0x6A97463: start_thread (pthread_create.c:333)
==2668== by 0x6D959DE: clone (clone.S:105)
--
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
mailing list