[Bug 783086] vpxenc: memory usage grows when dropframe-threshold is enabled
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Fri Aug 11 11:33:53 UTC 2017
https://bugzilla.gnome.org/show_bug.cgi?id=783086
George Kiagiadakis <gkiagia at tolabaki.gr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|git master |1.13.1
--- Comment #15 from George Kiagiadakis <gkiagia at tolabaki.gr> ---
commit 36fc2a747ade50db69221a502d498efa890bf054 (HEAD -> master, origin/master,
origin/HEAD)
Author: George Kiagiadakis <george.kiagiadakis at collabora.com>
Date: Thu Jul 27 17:21:48 2017 +0300
vpxenc: discard frames that have been dropped by libvpx
This fixes a memory leak. When dropframe-threshold has been set,
libvpx may output less frames than the input ones, which causes
some GstVideoCodecFrames to queue up in GstVideoEncoder's internal
frame queue with no chance of ever being all released. And because
the frames keep references to the input buffers, the input buffer
pool keeps allocating new buffers and memory usage grows very fast.
For example the following pipeline's memory usage grows at a rate
of about 1GB per minute!
videotestsrc ! capsfilter
caps=video/x-raw,width=1920,height=1080,framerate=30/1,format=I420 ! \
vp8enc target-bitrate=1000000 end-usage=cbr dropframe-threshold=95 !
fakesink
https://bugzilla.gnome.org/show_bug.cgi?id=783086
--
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