[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 #18 from soho123.2012 at gmail.com 2012-07-20 13:16:32 UTC ---
(In reply to comment #8)
> You can change some packages upwards, but only in one direction. Older
> base/good/ugly packages should (theoretically) continue to work fine if you
> just upgrade GStreamer core from 0.10.35 to 0.10.36.
> 
> So what you could try is: start with core/base .35, good .31, ugly .19, then:
> 
>  - upgrade core to .36, retest
>  - upgrade base to .36, retest
>  - upgrade good to .31, retest
>  - upgrade ugly to .19, retest  
> 
> However, in practice the assumption is that core/base are always of the same
> version, and modules released at the same time are used together, so there's no
> guarantee this is going to work, but it might.
> 
> A valgrind leak log from a desktop system would still also be useful. (Make
> sure to install -dbg packages for libc, glib, gstreamer libraries and gstreamer
> plugins before running valgrind).

Hi,

I have test 2 case:
1. core 36, base 35, good 30, ugly 18:
    the variation of free memory is not violent for about 6.5 hours
2. core 36, base 36, good 30, ugly 18:
    the variation of free memory is decrease about 3MB in 30minutes time
duration.
I can not use base 35 for good and ugly, since the configure procedure will get
error.
base 36 has memory leek issue on our platform. Even there is no memory leak
message on desktop platform fo far.
Do you have any idea about debugging base 36??

-- 
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.