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 344761 - gst-python leaks memory in initialization.
gst-python leaks memory in initialization.
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-python
git master
Other Linux
: Normal normal
: git master
Assigned To: Edward Hervey
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-13 13:25 UTC by Edward Hervey
Modified: 2012-12-17 11:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Edward Hervey 2006-06-13 13:25:19 UTC 
make check-valgrind in gst-python causes 2 leaks:

==26447== 17 (4 direct, 13 indirect) bytes in 1 blocks are definitely lost in loss record 519 of 1335
==26447==    at 0x1B909222: malloc (vg_replace_malloc.c:130)
==26447==    by 0xE17D2F: g_malloc (in /usr/lib/libglib-2.0.so.0.800.6)
==26447==    by 0x1BE611F9: init_gst (gstmodule.c:116)
==26447==    by 0xCD577F: _PyImport_LoadDynamicModule (in /usr/lib/libpython2.4.so.1.0)
==26447==    by 0xCD26E0: (within /usr/lib/libpython2.4.so.1.0)


==26447== 55 (28 direct, 27 indirect) bytes in 1 blocks are definitely lost in loss record 866 of 1335
==26447==    at 0x1B909B71: calloc (vg_replace_malloc.c:175)
==26447==    by 0xE17D9D: g_malloc0 (in /usr/lib/libglib-2.0.so.0.800.6)
==26447==    by 0xE1C718: g_option_context_new (in /usr/lib/libglib-2.0.so.0.800.6)
==26447==    by 0x1BEDE5B3: gst_init_check (gst.c:350)
==26447==    by 0x1BE6121C: init_gst (gstmodule.c:125)
==26447==    by 0xCD577F: _PyImport_LoadDynamicModule (in /usr/lib/libpython2.4.so.1.0)


I added suppressions for the time being in gst-python/testsuite/gstpython.supp
Comment 1 Edward Hervey 2006-06-13 14:43:46 UTC 
And yet another suppresion :

==6083== 4128 (4 direct, 4124 indirect) bytes in 1 blocks are definitely lost in loss record 655 of 4638
==6083==    at 0x1B909222: malloc (vg_replace_malloc.c:130)
==6083==    by 0xE17D2F: g_malloc (in /usr/lib/libglib-2.0.so.0.800.6)
==6083==    by 0xE02A6E: g_dir_open (in /usr/lib/libglib-2.0.so.0.800.6)
==6083==    by 0x1BF1EFB5: gst_registry_scan_path_level (gstregistry.c:750)
==6083==    by 0x1BF1F5A9: gst_registry_scan_path (gstregistry.c:867)
==6083==    by 0x1BEF408E: init_post (gst.c:678)
==6083==    by 0xE1E49A: g_option_context_parse (in /usr/lib/libglib-2.0.so.0.800.6)
==6083==    by 0x1BEF35D8: gst_init_check (gst.c:354)
==6083==    by 0x1BE6E21C: init_gst (gstmodule.c:125)
==6083==    by 0xCD577F: _PyImport_LoadDynamicModule (in /usr/lib/libpython2.4.so.1.0)
Comment 2 Sebastian Dröge (slomo) 2012-12-17 11:31:24 UTC 
Closing this bug now, gst-python is only an extension module to pygi now and this bug doesn't make much sense anymore in this context.