Discussion:
[Bug 778611] New: OpenGL Major memory leak when shutting down pipeline.
(too old to reply)
"GStreamer" (GNOME Bugzilla)
2017-02-14 15:16:27 UTC
Permalink
Raw Message
https://bugzilla.gnome.org/show_bug.cgi?id=778611

Bug ID: 778611
Summary: OpenGL Major memory leak when shutting down pipeline.
Classification: Platform
Product: GStreamer
Version: 1.11.1
OS: Linux
Status: NEW
Severity: major
Priority: Normal
Component: gst-plugins-bad
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: ***@duotecno.be
QA Contact: gstreamer-***@lists.freedesktop.org
GNOME version: ---

Created attachment 345737
--> https://bugzilla.gnome.org/attachment.cgi?id=345737&action=edit
Shows memory usage before opening a pipeline.

I have a working application.
In my application I always shutdown the pipeline and make a new pipeline for
every new video source.

For performance issues I reworked the original pipeline:

gst-launch-1.0
souphttpsrc location=<URL> is-live=true ! \
image/jpeg,framerate=25/1 !
jpegparse !
omxmjpegdec !
videoconvert !
videoscale add-borders=true !
video/x-raw,framerate=25/1,format=RGBx,width=800,height=480 !
autovideosink

to:

gst-launch-1.0 souphttpsrc location=<URL> is-live=true ! \
image/jpeg,framerate=25/1 ! \
jpegparse ! \
omxmjpegdec ! \
glupload ! \
glcolorconvert ! \
glcolorscale ! \
"video/x-raw(memory:GLMemory),framerate=25/1,width=800,height=480" ! \
videorate \
glimagesink


CPU is decreased a lot but there is a major memory leak.
After 10-20 times shutting down the pipeline and creating a new pipeline the
application crashed because of memory allocation problems.
I have replaced omxmjpegdec with jpegdec decoder and the problem is the same.
With the original pipeline the application has been running for days...

logging1.txt: Shows memory usage before opening a pipeline.
logging2.txt: Shows memory usage after several shutdown and creating new
pipelines.
logging3.txt: Shows error message that memory cannot be allocated anymore.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
"GStreamer" (GNOME Bugzilla)
2017-02-14 15:17:04 UTC
Permalink
Raw Message
https://bugzilla.gnome.org/show_bug.cgi?id=778611

Tom Mitchell <***@duotecno.be> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@duotecno.be

--- Comment #1 from Tom Mitchell <***@duotecno.be> ---
Created attachment 345738
--> https://bugzilla.gnome.org/attachment.cgi?id=345738&action=edit
Shows memory usage after several shutdown and creating new pipelines.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
"GStreamer" (GNOME Bugzilla)
2017-02-14 15:17:46 UTC
Permalink
Raw Message
https://bugzilla.gnome.org/show_bug.cgi?id=778611

--- Comment #2 from Tom Mitchell <***@duotecno.be> ---
Created attachment 345739
--> https://bugzilla.gnome.org/attachment.cgi?id=345739&action=edit
Shows error message that memory cannot be allocated anymore.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
"GStreamer" (GNOME Bugzilla)
2017-11-06 13:24:17 UTC
Permalink
Raw Message
https://bugzilla.gnome.org/show_bug.cgi?id=778611

Matthew Waters (ystreet00) <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |***@gmail.com

--- Comment #3 from Matthew Waters (ystreet00) <***@gmail.com> ---
This could be a duplicate of bug 788280. Can you try with latest master and
report if your issue has been fixed?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
Loading...