Memory leak problem with souphttpsrc and qtdemux
Locked
 
|
I have very strange issue with usage of souphttpsrc plugin. I am using qtdemux for demultiplexing .mp4 files and I am detecting memory leak when input source is souphttpsrc. Problem is still present even when I reduce the pipeline like this:
gst-launch souphttpsrc location="http://www.youtube.com/get_video?fmt=18&video_id=0pkMzSphwM0&t=vjVQa1PpcFNtjh0WrsbPfZe68XzvSyNJzci0R4tTg4s%3D" ! qtdemux name=demux demux.video_00 ! fakesink In the case when input source is filesrc I don't have such problem. This is reduced pipeline example for this case: gst-launch filesrc location=test.mp4 ! qtdemux name=demux demux.video_00 ! fakesink Target platform is MIPS. I have the same problem if I use neonhttpsrc as input source or flvdemux as demux. I spent two weeks to locate and solve this problem but without any progress. Has anyone faced similar problem? Any hint will be very helpful for me! |
Re: Memory leak problem with souphttpsrc and qtdemux
|
|
How do you detect the leak?
Is it possible that it's just the demuxer that keeps on queuing up audio data until something is attached to the audio src pad? Regards, Arnout On Friday 06 November 2009 17:51:40, tiki_ns wrote: > I have very strange issue with usage of souphttpsrc plugin. I am using > qtdemux for demultiplexing .mp4 files and I am detecting memory leak when > input source is souphttpsrc. Problem is still present even when I reduce > the pipeline like this: > > gst-launch souphttpsrc > location="http://www.youtube.com/get_video?fmt=18&video_id=0pkMzSphwM0&t= > vjVQa1PpcFNtjh0WrsbPfZe68XzvSyNJzci0R4tTg4s%3D" ! qtdemux name=demux > demux.video_00 ! fakesink > > In the case when input source is filesrc I don't have such problem. This > is reduced pipeline example for this case: > > gst-launch filesrc location=test.mp4 ! qtdemux name=demux demux.video_00 > ! fakesink > > Target platform is MIPS. I have the same problem if I use neonhttpsrc as > input source or flvdemux as demux. > > I spent two weeks to locate and solve this problem but without any > progress. Has anyone faced similar problem? Any hint will be very > helpful for me! > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
I am monitoring memory usage with linux top process (just gst pipeline is active). I reduced pipeline to src/demux/sink just to isolate problematic block. Memory leak is present even in case when audio pad is attached. When I change input source to filesrc I don't have such problem but I have to use some http source.
Regards, Tiki
|
Re: Memory leak problem with souphttpsrc and qtdemux
|
|
What if you put a queue between filesrc and qtdemux? That will make
effectively make the source a push source. If the leak is still present, the problem is in qtdemux. Philip On Mon, Nov 9, 2009 at 09:27, tiki_ns <[hidden email]> wrote: > > I am monitoring memory usage with linux top process (just gst pipeline is > active). I reduced pipeline to src/demux/sink just to isolate problematic > block. Memory leak is present even in case when audio pad is attached. When > I change input source to filesrc I don't have such problem but I have to use > some http source. > > > Regards, > Tiki > > > Arnout Vandecappelle wrote: >> >> How do you detect the leak? >> >> Is it possible that it's just the demuxer that keeps on queuing up audio >> data until something is attached to the audio src pad? >> >> Regards, >> Arnout >> >> On Friday 06 November 2009 17:51:40, tiki_ns wrote: >>> I have very strange issue with usage of souphttpsrc plugin. I am using >>> qtdemux for demultiplexing .mp4 files and I am detecting memory leak when >>> input source is souphttpsrc. Problem is still present even when I reduce >>> the pipeline like this: >>> >>> gst-launch souphttpsrc >>> location="http://www.youtube.com/get_video?fmt=18&video_id=0pkMzSphwM0&t= >>> vjVQa1PpcFNtjh0WrsbPfZe68XzvSyNJzci0R4tTg4s%3D" ! qtdemux name=demux >>> demux.video_00 ! fakesink >>> >>> In the case when input source is filesrc I don't have such problem. This >>> is reduced pipeline example for this case: >>> >>> gst-launch filesrc location=test.mp4 ! qtdemux name=demux demux.video_00 >>> ! fakesink >>> >>> Target platform is MIPS. I have the same problem if I use neonhttpsrc as >>> input source or flvdemux as demux. >>> >>> I spent two weeks to locate and solve this problem but without any >>> progress. Has anyone faced similar problem? Any hint will be very >>> helpful for me! >>> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> gstreamer-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> >> > > -- > View this message in context: http://old.nabble.com/Memory-leak-problem-with-souphttpsrc-and-qtdemux-tp26230825p26262708.html > Sent from the GStreamer-devel mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > -- Philip Jägenstedt ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Re: Memory leak problem with souphttpsrc and qtdemux
|
|
In reply to this post by tiki_ns
On Mon, 2009-11-09 at 00:27 -0800, tiki_ns wrote:
> I am monitoring memory usage with linux top process (just gst pipeline is > active). I reduced pipeline to src/demux/sink just to isolate problematic > block. Memory leak is present even in case when audio pad is attached. When > I change input source to filesrc I don't have such problem but I have to use > some http source. I did not observe any leaks using souphttpsrc/qtdemux from git with valgrind. FWIW, filesrc ! queue ! qtdemux ! .. should use the same codepath as souphttpsrc ! qtdemux (ie. push-based operation). Cheers -Tim ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
In reply to this post by Philip Jägenstedt
I have tried adding the queue in front of qtdemux for filesrc and memory leak is present! If I use long enough file, memory usage rises above 78% and sometimes the application is killed. The same behavior I observed when I used souphttpsrc, only now with filesrc the rate at which memory usage rises is even higher. I recently joined GST world and so I am still not familiar with it's concept. Is it possible that such memory issue exist in qtdemux and flvdemux as well?
One more thing, I am not using the latest version of gst and plugins because of some stability issues on target platform so I will try to update to latest one to check if issue still exist. Thank you very much for your information and support. I will inform you about any progress. Best regards, Tiki
|
|
|
I want just to inform you. I updated my SW to use latest version of GST plugins and I don't have problem with "qtdemux memory leak".
Thank you very much for your help. Regards, Tiki
|
«
Return to GStreamer-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |