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 306938 - memory leak in gsttypefind
memory leak in gsttypefind
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: 0.8.10
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-08 19:31 UTC by Luca Ognibene
Modified: 2005-06-09 10:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Luca Ognibene 2005-06-08 19:31:09 UTC 
As reported by valgrind:
==9489== 32 bytes in 2 blocks are definitely lost in loss record 6 of 27
==9489==    at 0x1B904EDD: malloc (vg_replace_malloc.c:131)
==9489==    by 0x1BA6AAD6: g_malloc (in /usr/lib/libglib-2.0.so.0.600.3)
==9489==    by 0x1C77D888: plugin_init (gsttypefindfunctions.c:1827)
==9489==    by 0x1B94A7C8: gst_plugin_register_func (gstplugin.c:214)
==9489==    by 0x1B94AFB3: gst_plugin_load_file (gstplugin.c:464)
==9489==    by 0x1B9741D2: gst_xml_registry_load_plugin (gstlibxmlregistry.c:969)
==9489==    by 0x1B967FD2: gst_registry_load_plugin (gstregistry.c:450)
==9489==    by 0x1B94C071: gst_plugin_feature_ensure_loaded (gstpluginfeature.c:108)
==9489==    by 0x1B95F395: gst_type_find_load_plugin (gsttypefind.c:121)
==9489==    by 0x1B95F691: gst_type_find_factory_call_function (gsttypefind.c:202)
Comment 1 Ronald Bultje 2005-06-09 10:01:15 UTC 
  TYPE_FIND_REGISTER_START_WITH (plugin, "audio/x-au", GST_RANK_MARGINAL,
      au_exts, ".snd", 4, GST_TYPE_FIND_MAXIMUM);
  TYPE_FIND_REGISTER_START_WITH (plugin, "audio/x-au", GST_RANK_MARGINAL,
      au_exts, "dns.", 4, GST_TYPE_FIND_MAXIMUM);

The first is the memleak; does the second overwrite the first? That's the only
point where I can see a memleak... In that case AU would need a full-fledged
function...
Comment 2 Ronald Bultje 2005-06-09 10:08:05 UTC 
Fixed that, should be fine now...