[Bug 680144] gstreamer 0.10.36 has memory leak issue

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=680144
  GStreamer | gstreamer (core) | 0.10.36

--- Comment #19 from soho123.2012 at gmail.com 2012-07-20 14:42:46 UTC ---
(In reply to comment #15)
> No, it means something is not right. It should look similar to this (the
> ===12345=== bits are from valgrind):
> 
> $ G_SLICE=always-malloc valgrind --leak-check=yes --trace-children=yes /bin/ls
> /does/not/exist
> ==16459== Memcheck, a memory error detector
> ==16459== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
> ==16459== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
> ==16459== Command: /bin/ls /does/not/exist
> ==16459== 
> /bin/ls: cannot access /does/not/exist: No such file or directory
> ==16459== 
> ==16459== HEAP SUMMARY:
> ==16459==     in use at exit: 19,312 bytes in 3 blocks
> ==16459==   total heap usage: 100 allocs, 97 frees, 32,216 bytes allocated
> ==16459== 
> ==16459== LEAK SUMMARY:
> ==16459==    definitely lost: 0 bytes in 0 blocks
> ==16459==    indirectly lost: 0 bytes in 0 blocks
> ==16459==      possibly lost: 0 bytes in 0 blocks
> ==16459==    still reachable: 19,312 bytes in 3 blocks
> ==16459==         suppressed: 0 bytes in 0 blocks
> ==16459== Reachable blocks (those to which a pointer was found) are not shown.
> ==16459== To see them, rerun with: --leak-check=full --show-reachable=yes
> ==16459== 
> ==16459== For counts of detected and suppressed errors, rerun with: -v
> ==16459== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)

Hi, 

After a period of observation, in desktop test case,
the free memory is descreasing,
8MB for about 3 hours, from the output of "top" utility

this is the same trend as our embedded platform,
it seems beas 0.10.36 has memory leak issue,
Do you know any bug fix about memory leak for base 0.10.36?

Thanks !

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.