[gstreamer-bugs] [Bug 307260] Leak in the registry code

[bugzilla-daemon at bugzilla.gnome.org]

Do not reply to this email.  You can add comments to this bug at
 http://bugzilla.gnome.org/show_bug.cgi?id=307260
 GStreamer | gstreamer (core) | Ver: HEAD CVS





------- Additional Comments From Kjartan Maraas  2005-09-12 16:25 -------
Fresh traces with gnome 2.12 and the 0.8 branch of gstreamer:

==4882== 804 bytes in 164 blocks are definitely lost in loss record 4780 of 4931
==4882==    at 0x1B901862: malloc (vg_replace_malloc.c:149)
==4882==    by 0x1C816C65: g_malloc (gmem.c:137)
==4882==    by 0x1C827499: g_strdup (gstrfuncs.c:91)
==4882==    by 0x1B9DAA05: read_string (gstlibxmlregistry.c:590)
==4882==    by 0x1B9DAC59: load_plugin (gstlibxmlregistry.c:836)
==4882==    by 0x1B9DB495: gst_xml_registry_load (gstlibxmlregistry.c:928)
==4882==    by 0x1B9D15AB: gst_registry_load (gstregistry.c:125)
==4882==    by 0x1B9D20A5: _registry_load_func (gstregistrypool.c:110)
==4882==    by 0x1C80DC5F: g_list_foreach (glist.c:670)
==4882==    by 0x1B9D20CF: gst_registry_pool_load_all (gstregistrypool.c:125)
==4882==    by 0x1B995C64: init_post (gst.c:643)
==4882==    by 0x1B995FA1: gst_init_check_with_popt_table (gst.c:343)
==4882==    by 0x1B995FF5: gst_init_with_popt_table (gst.c:288)
==4882==    by 0x1B996034: gst_init (gst.c:267)
==4882==    by 0x8066839: acme_volume_gstreamer_class_intern_init
(acme-volume-gstreamer.c:359)
==4882==    by 0x1C7D69DF: g_type_class_ref (gtype.c:1908)
==4882==    by 0x1C7BF198: g_object_newv (gobject.c:824)
==4882==    by 0x1C7BF58C: g_object_new_valist (gobject.c:951)
==4882==    by 0x1C7BF701: g_object_new (gobject.c:789)
==4882==    by 0x8065EF7: acme_volume_new (acme-volume.c:104)
==4882==    by 0x8057392: gnome_settings_multimedia_keys_load
(gnome-settings-multimedia-keys.c:951)
==4882==    by 0x80552E9: gnome_settings_daemon_new (gnome-settings-daemon.c:401)
==4882==    by 0x8054018: main (factory.c:42)


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