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

[bugzilla-daemon at bugzilla.gnome.org]

Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=307260
 GStreamer | gstreamer (core) | Ver: HEAD CVS





------- Additional Comments From Kjartan Maraas  2005-08-28 11:39 -------
Another one:

==19863== 601 (36 direct, 565 indirect) bytes in 3 blocks are definitely lost in
loss record 3471 of 3818
==19863==    at 0x1B903882: malloc (vg_replace_malloc.c:149)
==19863==    by 0x1C81BBB1: g_malloc (gmem.c:137)
==19863==    by 0x1C8077BE: g_error_new_valist (gerror.c:41)
==19863==    by 0x1C8079FA: g_set_error (gerror.c:205)
==19863==    by 0x1B9BB508: gst_plugin_check_module (gstplugin.c:327)
==19863==    by 0x1B9BBC59: gst_plugin_load_file (gstplugin.c:412)
==19863==    by 0x1B9DD5AF: gst_xml_registry_load_plugin (gstlibxmlregistry.c:969)
==19863==    by 0x1B9D3CA6: gst_registry_load_plugin (gstregistry.c:450)
==19863==    by 0x1B9BCA61: gst_plugin_feature_ensure_loaded
(gstpluginfeature.c:108)
==19863==    by 0x1B9A9833: gst_element_factory_create (gstelementfactory.c:297)
==19863==    by 0x80636F4: acme_volume_gstreamer_open (acme-volume-gstreamer.c:262)
==19863==    by 0x8063BF3: acme_volume_gstreamer_init (acme-volume-gstreamer.c:339)
==19863==    by 0x1C7DBE43: g_type_create_instance (gtype.c:1596)
==19863==    by 0x1C7C33AB: g_object_constructor (gobject.c:1011)
==19863==    by 0x1C7C3A07: g_object_newv (gobject.c:908)
==19863==    by 0x1C7C4518: g_object_new_valist (gobject.c:951)
==19863==    by 0x1C7C468D: g_object_new (gobject.c:789)
==19863==    by 0x806333F: acme_volume_new (acme-volume.c:104)
==19863==    by 0x80547AA: gnome_settings_multimedia_keys_load
(gnome-settings-multimedia-keys.c:951)
==19863==    by 0x8052709: gnome_settings_daemon_new (gnome-settings-daemon.c:401)
==19863==    by 0x8051438: 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.