GNOME Bugzilla – Bug 408278
[videorate] memory leak
Last modified: 2007-02-16 10:15:17 UTC
I found a memory leak of caps with gstvideorate with this pipeline gst-launch-0.10 -v videotestsrc num-buffers=10 ! videorate ! fakesink will add the patch soon
Created attachment 82611 [details] [review] patch for this bug before fix (valgrind output) : ==20910== LEAK SUMMARY: ==20910== definitely lost: 36 bytes in 1 blocks. ==20910== indirectly lost: 120 bytes in 10 blocks. ==20910== possibly lost: 0 bytes in 0 blocks. ==20910== still reachable: 364,398 bytes in 5,237 blocks. after fix (less reachable memory): ==8391== LEAK SUMMARY: ==8391== definitely lost: 36 bytes in 1 blocks. ==8391== indirectly lost: 120 bytes in 10 blocks. ==8391== possibly lost: 0 bytes in 0 blocks. ==8391== still reachable: 155,636 bytes in 2,279 blocks.
Can't make this show up in valgrind for me, but the patch is obviously correct. Applied to CVS, thanks! 2007-02-16 Tim-Philipp Müller <tim at centricular dot net> Patch by: Yves Lefebvre <ivanohe abacom com> * gst/videorate/gstvideorate.c: (gst_video_rate_setcaps): Don't leak caps. Fixes #408278.