Memory Leak?
rland
rlandjon at gmail.com
Fri Jun 8 02:08:21 UTC 2018
killerrats wrote
> I was recording with this pipeline for more than 3 days. At the end of the
> third day the memory was crazy big. it was above 200 mb in memory.
> Pipeline:
>
> gst-launch-1.0 -e rtspsrc location=[IP] name=source ! rtph264depay !
> h264parse ! mux.video splitmuxsink max-size-bytes=10485760 max-files=10240
> muxer=avimux location=video%06d.avi name=mux source. ! rtpmp4gdepay !
> aacparse ! mux.audio_0
You can run valgrind to check where
there may be memory leak,note that
pay attention to the "definitely lost" parts in summary. :)
Like this:
valgrind -v --tool=memcheck --track-fds=yes --leak-check=full
--show-reachable=yes --time-stamp=yes --undef-value-errors=no
--malloc-fill=0xc --free-fill=0xd --freelist-vol=100000000
--trace-children=yes --num-callers=50
--suppressions=gstreamer-1.0-1.14.0/common/gst.supp --log-file=valgrind_gst
gst-launch-1.0 -e rtspsrc location=[IP] name=source ! rtph264depay !
h264parse ! mux.video splitmuxsink max-size-bytes=10485760 max-files=10240
muxer=avimux location=video%06d.avi name=mux source. ! rtpmp4gdepay !
aacparse ! mux.audio_0
--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
More information about the gstreamer-devel
mailing list