[Bug 687493] Huge memory leak using Python, Gtk+, GStreamer and vp8enc

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Sun May 5 12:09:25 PDT 2013


https://bugzilla.gnome.org/show_bug.cgi?id=687493
  GStreamer | don't know | 1.0.1

--- Comment #15 from David Klasinc <bigwhale at lubica.net> 2013-05-05 19:09:20 UTC ---
I just confirmed the case with gst-launch. Here are the command lines used:

No leak, terrible framerate:
gst-launch-1.0 -e ximagesrc endx=1919 endy=1079 use-damage=false
show-pointer=true ! queue ! videorate ! video/x-raw,framerate=25/1 !
videoconvert !  vp8enc end-usage=vbr cpu-used=6 target-bitrate=80000000
threads=4 token-partitions=2 min-quantizer=10 max-quantizer=30 ! queue
name=before_mux ! webmmux name=mux ! queue ! filesink
location="test-videorate.webm"

Leak, excellent framerate:
gst-launch-1.0 -e ximagesrc endx=1919 endy=1079 use-damage=false
show-pointer=true ! queue ! videorate ! video/x-raw,framerate=25/1 !
videoconvert !  vp8enc end-usage=vbr cpu-used=6 target-bitrate=80000000
threads=4 token-partitions=2 min-quantizer=10 max-quantizer=30 deadline=100000
! queue name=before_mux ! webmmux name=mux ! queue ! filesink
location="test-videorate.webm"

The only difference is in the deadline parameter. If deadline is set to around
42000 or more, memory stars leaking.

gst-launch is probably written in C, so this should be enough, I guess?

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


More information about the gstreamer-bugs mailing list