[gst-devel] "Possibly lost" memory shown by valgrind during gst_init_check()

[Aniruddha]

Hello People,
                    I am using gstreamer for my application. 
When i ran valgrind on my code, the valgrind log showed many
occurances of "possibly lost" memory leaks during gst_init_check().
One of such log is as shown below :-

==29362== 40 bytes in 1 blocks are possibly lost in loss record 2,538 of 3,792
==29362==    at 0x400473F: calloc (vg_replace_malloc.c:279)
==29362==    by 0x4056C94: g_malloc0 (gmem.c:151)
==29362==    by 0x42D499F: type_node_any_new_W (gtype.c:395)
==29362==    by 0x42D4B34: type_node_fundamental_new_W (gtype.c:500)
==29362==    by 0x42D8CEC: g_type_register_fundamental (gtype.c:2379)
==29362==    by 0x4164C56: gst_fraction_get_type (gstvalue.c:4023)
==29362==    by 0x4167FDE: _gst_value_initialize (gstvalue.c:4158)
==29362==    by 0x4106DE5: init_post (gst.c:1058)
==29362==    by 0x405CC3F: g_option_context_parse (goption.c:1796)
==29362==    by 0x41065A4: gst_init_check (gst.c:430)

Please suggest.

Regards
Aniruddha

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20090723/a15fb259/attachment.htm>