After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 778611 - OpenGL Major memory leak when shutting down pipeline.
OpenGL Major memory leak when shutting down pipeline.
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
1.11.1
Other Linux
: Normal major
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-02-14 15:16 UTC by Tom Mitchell
Modified: 2018-04-12 17:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Shows memory usage before opening a pipeline. (8.64 KB, text/plain)
2017-02-14 15:16 UTC, Tom Mitchell
Details
Shows memory usage after several shutdown and creating new pipelines. (132.52 KB, text/plain)
2017-02-14 15:17 UTC, Tom Mitchell
Details
Shows error message that memory cannot be allocated anymore. (5.36 KB, text/plain)
2017-02-14 15:17 UTC, Tom Mitchell
Details

Description Tom Mitchell 2017-02-14 15:16:27 UTC
Created attachment 345737 [details]
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.
Comment 1 Tom Mitchell 2017-02-14 15:17:04 UTC
Created attachment 345738 [details]
Shows memory usage after several shutdown and creating new pipelines.
Comment 2 Tom Mitchell 2017-02-14 15:17:46 UTC
Created attachment 345739 [details]
Shows error message that memory cannot be allocated anymore.
Comment 3 Matthew Waters (ystreet00) 2017-11-06 13:24:17 UTC
This could be a duplicate of bug 788280. Can you try with latest master and report if your issue has been fixed?
Comment 4 Tim-Philipp Müller 2018-04-12 17:53:30 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!