Difference between revisions of "Debugging Memory Leaks on GStreamer by analyzing reference counters"
From RidgeRun Developer Connection
|(2 intermediate revisions by the same user not shown)|
|−|Looking for memory leaks in programs is a very challenging problem. This is even more true for embedded systems, since some of the best tools for this aren't always available (like valgrind), or are difficult to use on this environment (like compile-time hacks, since you depend on other libraries that you may not be able to recompile). |+|
for memory leaks]]
|−|[[Category:GStreamer]] [[Category:Whitepaper]] |+|
Latest revision as of 14:31, 16 October 2012
See GStreamer Debugging#Look for memory leaks