After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 168135 - [xmlregistry] Mem leak in loading plugins
[xmlregistry] Mem leak in loading plugins
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-02-22 10:21 UTC by Luca Ognibene
Modified: 2005-08-26 00:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Luca Ognibene 2005-02-22 10:21:28 UTC 
valgrind gst-launch-0.8 fakesrc ! fakesink

==10542== 2912 bytes in 48 blocks are definitely lost in loss record 17 of 23
==10542==    at 0x1B905901: calloc (vg_replace_malloc.c:176)
==10542==    by 0x1BA68ABE: g_malloc0 (gmem.c:154)
==10542==    by 0x1B982E3B: gst_xml_registry_start_element (gstxmlregistry.c:944)
==10542==    by 0x1BA67564: g_markup_parse_context_parse (gmarkup.c:1321)
==10542==    by 0x1B981ED9: gst_xml_registry_load (gstxmlregistry.c:675)
==10542==    by 0x1B9764F7: gst_registry_load (gstregistry.c:125)
==10542==    by 0x1B97723B: _registry_load_func (gstregistrypool.c:110)
==10542==    by 0x1BA603EE: g_list_foreach (glist.c:670)
==10542==    by 0x1B977271: gst_registry_pool_load_all (gstregistrypool.c:125)
==10542==    by 0x1B9300F4: init_post (gst.c:641)

This one is harder for me.. (don't know gst core!). I'll take a look anyway..
Comment 1 Ronald Bultje 2005-02-25 08:36:53 UTC 
Hm... The allocated block is added to the list of available plugins, is that
really a leak? Unless we forget to free if a part failed to load... Can you run
with --gst-debug-level=5 to see at which point this leak occurs exactly?
Comment 2 Luca Ognibene 2005-02-28 13:48:17 UTC 
Sorry but i can't reproduce it anymore.. Maybe it was a broken installation.. If
i'll be able to reproduce it i'll reopen this bug.