[Bug 762929] New: simple transcoding pipeline takes over 4GB RAM
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Tue Mar 1 15:47:11 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=762929
Bug ID: 762929
Summary: simple transcoding pipeline takes over 4GB RAM
Classification: Platform
Product: GStreamer
Version: unspecified
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gstreamer (core)
Assignee: gstreamer-bugs at lists.freedesktop.org
Reporter: exebook at gmail.com
QA Contact: gstreamer-bugs at lists.freedesktop.org
GNOME version: ---
Created attachment 322785
--> https://bugzilla.gnome.org/attachment.cgi?id=322785&action=edit
dot file for the pipeline that causes the issue
I have been told on IRC that this kind of simple transcoding should take about
500 MB RAM, but I experience huge RAM usage even above 4GB. I measure RSS.
(Resident Set Size) on Ubuntu.
I have been trying various types of input streams with about the same results.
The memory consumption grows after hours. But will peak at about 4GB and not
grow since then. With a few transcoders running, the kernel will start killing
them.
Most of memory is consumed by x264enc, but the mpegdecoder is also hungry. I
can tell this from vagrind --massif. I cannot attach two files here I guess. I
never got 4GB consumption under vagrind/massif, I think because it runs slower.
Not sure if this is considered a bug, but since I've been told that is should
definitely be under 1 GB I think there is a chance it is.
--
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