[Bug 707523] d3dvideosink memleak

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=707523
  GStreamer | gst-plugins-bad | 1.x

--- Comment #34 from Steven <jsteve3000 at gmail.com> 2014-07-16 09:55:59 UTC ---
(In reply to comment #33)
> maybe, for test purpose you could try to modify your parse_launch line to use
> only one d3dvideosink, 
> 
> if you see no leak with a single d3dvideosink element is the same problem
> initially reported

I have tested my app using your suggested approach. My original and test
pipelines are given below. The memory leak is exactly the same in both cases.

Original Pipeline:
uridecodebin name=vehiclebin uri=rtsp://127.0.0.1:8554/vehicle.sdp !
tee name=tp
tp. ! queue ! videocrop top=0   left=10  right=376 bottom=290 ! autovideosink
name=rear
tp. ! queue ! videocrop top=0   left=400 right=0   bottom=290 ! autovideosink
name=forward
tp. ! queue ! videocrop top=290 left=10  right=376 bottom=6   ! autovideosink
name=left
tp. ! queue ! videocrop top=290 left=398 right=0   bottom=6   ! autovideosink
name=right

Test Pipeline:
uridecodebin name=vehiclebin uri=rtsp://127.0.0.1:8554/vehicle.sdp !
autovideosink name=forward

---

On a side note d3dvideosink is no longer stretching the video to fill the
window / control. The scaling method now maintains aspect ratio. Can I change
this back myself with an option or is it in the code?

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