[Bug 702632] acceptcaps query can be very very slow

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=702632
  GStreamer | gstreamer (core) | git

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |
           Severity|normal                      |blocker

--- Comment #5 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2013-06-23 12:21:36 UTC ---
This change:

 commit 1815e6067a1077ddb92330b25f172da82f38a3e8
 Author: Sjoerd Simons <sjoerd.simons at collabora.co.uk>
 Date:   Wed Jun 19 12:30:47 2013 +0200

    pad: Add a filter to the caps_query done by acceptcaps

appears to break at least these unit tests in gst-plugins-good (reverting it
makes them pass again):   


Running suite(s): rtp_data_test

Error from element appsrc1: Internal data flow error.
gstbasesrc.c(2812): gst_base_src_loop ():
/GstPipeline:rtph263ppay-identity-pipeline/GstAppSrc:appsrc1:
streaming task paused, reason not-negotiated (-4)


Error from element appsrc2: Internal data flow error.
gstbasesrc.c(2812): gst_base_src_loop ():
/GstPipeline:rtph263ppay-identity-pipeline/GstAppSrc:appsrc2:
streaming task paused, reason not-negotiated (-4)

100%: Checks: 29, Failures: 0, Errors: 0
PASS: elements/rtp-payloading  [well, should really say FAIL here]

Running suite(s): rtpmux
0%: Checks: 3, Failures: 3, Errors: 0
elements/rtpmux.c:187:F:rtpmux_basic:test_rtpmux_basic:0: Assertion
'gst_pad_push (src1, inbuf) == GST_FLOW_OK' failed
elements/rtpmux.c:187:F:rtpdtmfmux_basic:test_rtpdtmfmux_basic:0: Assertion
'gst_pad_push (src1, inbuf) == GST_FLOW_OK' failed
elements/rtpmux.c:187:F:rtpdtmfmux_lock:test_rtpdtmfmux_lock:0: Assertion
'gst_pad_push (src1, inbuf) == GST_FLOW_OK' failed
FAIL: elements/rtpmux

-- 
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.