[Bug 790833] VmSize remains high after clean up

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=790833

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |t.i.m at zen.co.uk

--- Comment #1 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
What is the actual bug you're reporting?

$ valgrind --leak-check=yes ./test 

 LEAK SUMMARY:
    definitely lost: 16,384 bytes in 1 blocks [this is one-time allocs in glib]
    indirectly lost: 0 bytes in 0 blocks
      possibly lost: 4,228 bytes in 61 blocks
    still reachable: 551,489 bytes in 2,042 blocks
                       of which reachable via heuristic:
                         length64           : 280 bytes in 7 blocks
                         newarray           : 1,568 bytes in 18 blocks
         suppressed: 0 bytes in 0 blocks

This looks fine to me. There are some fair bit of global allocations that will
be around until the process ends, e.g. for the type system.

Running multiple loops of the pipeline also doesn't increase anything.

Maybe VMSize is simply not right for what you want to measure? Compare to Rss*

You can check /proc/self/maps for details.

Loading GStreamer plugins involves loading shared libs and those won't be
unloaded ever. This is not really a problem.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.