GNOME Bugzilla – Bug 784276
level: Memory leak
Last modified: 2017-07-24 11:38:32 UTC
Memory leak in level element when messages is enabled. gst-launch-1.0 audiotestsrc ! level interval=100000 message=false ! fakesink --gst-debug=3 I used Linux top command to check the Memory usage. Running pipeline for long time makes system unstable. With below pipeline memory leak is not observer. gst-launch-1.0 audiotestsrc ! level interval=100000 message=true ! fakesink --gst-debug=3 I tried to run pipeline through valgrind no lead reported by the tool. ==16178== LEAK SUMMARY: ==16178== definitely lost: 0 bytes in 0 blocks ==16178== indirectly lost: 0 bytes in 0 blocks ==16178== possibly lost: 4,636 bytes in 61 blocks ==16178== still reachable: 299,866 bytes in 1,966 blocks ==16178== of which reachable via heuristic: ==16178== length64 : 280 bytes in 7 blocks ==16178== newarray : 1,568 bytes in 18 blocks ==16178== suppressed: 0 bytes in 0 blocks I am using gstreamer-1.12.1 for testing.
The pipeline with message=true uses a lot of memory here, the one with message=false doesn't. Did you mix them up? Reason for the high, always increasing memory usage with message=true is that a message is posted on the bus for every single audio sample (100 microseconds), and they are not taken from the bus faster than that.
Maybe we should just make level warn if the interval is set too low? (Assuming we won't be able to come up with a min value that we could put into the paramspec)
@Sebastian Dröge Yes I interchanged the pipelines. Sorry With message post memory leak is seen. I have run test cases for long duration by increasing the interval to 3 secs. I will check the memory usage after 48 hours.
No memory leak is not seen with 200msec interval, after weeks of long run. Not a bug, it was configuration issue. Thank you.