gstreamer/tests/check
Sebastian Dröge 2aa9ad9c62 Revert "pad: Handle changing sticky events in pad probes"
This reverts commit 11e0f451eb.

When pushing a sticky event out of a pad with a pad probe or pad offset,
those should not be applied to the event that is actually stored in the
event but only in the event sent downstream. The pad probe and pad
offsets are conceptually *after* the pad, added by external code and
should not affect any internal state of pads/elements.

Also storing the modified event has the side-effect that a re-sent event
would arrive with any previous modifications done by the same pad probe
again inside that pad probe, and it would have to check if its
modifications are already applied or not.

For sink pads and generally for events arriving in a pad, some further
changes are still needed and those are tracked in
  https://bugzilla.gnome.org/show_bug.cgi?id=765049

In addition, the commit also had a refcounting problem with events,
causing already destroyed events to be stored inside pads.
2018-07-23 23:17:54 +03:00
..
elements Fix typos in comments and docs 2018-05-01 11:18:03 +01:00
generic tests: include config.h and don't include unix headers 2017-11-24 13:41:20 +01:00
gst Revert "pad: Handle changing sticky events in pad probes" 2018-07-23 23:17:54 +03:00
libs bitwriter: Add unit tests 2018-05-06 17:05:27 +02:00
pipelines tests: fix message leak in seek test 2017-04-19 13:39:46 +01:00
tools tests: refactor tools check a little 2014-10-31 16:10:01 +00:00
.gitignore tests: add check for gst-inspect --exists functionality 2012-09-01 23:02:10 +01:00
Makefile.am bitwriter: Add unit tests 2018-05-06 17:05:27 +02:00
meson.build bitwriter: Add unit tests 2018-05-06 17:05:27 +02:00