GNOME Bugzilla – Bug 778611
OpenGL Major memory leak when shutting down pipeline.
Last modified: 2018-04-12 17:53:30 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.
Created attachment 345738 [details] Shows memory usage after several shutdown and creating new pipelines.
Created attachment 345739 [details] Shows error message that memory cannot be allocated anymore.
This could be a duplicate of bug 788280. Can you try with latest master and report if your issue has been fixed?
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!