[Bug 760821] tracerrecord: Fix memory leaks and mishandlings

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=760821

--- Comment #3 from Vineeth <vineeth.tm at samsung.com> ---
Created attachment 319324
  --> https://bugzilla.gnome.org/attachment.cgi?id=319324&action=edit
tests: fix memory leaks

Fix for below memory leaks

tracer_record

==1272== 166 (64 direct, 102 indirect) bytes in 1 blocks are definitely lost in
loss record 1,475 of 1,503
==1272==    at 0x402C17C: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==1272==    by 0x423EBE2: g_malloc (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==1272==    by 0x4255281: g_slice_alloc (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==1272==    by 0x425579C: g_slice_alloc0 (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==1272==    by 0x41CFACD: g_type_create_instance (in
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4002.0)
==1272==    by 0x41B28FD: ??? (in
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4002.0)
==1272==    by 0x41B4D96: g_object_new_valist (in
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4002.0)
==1272==    by 0x41B4FEF: g_object_new (in
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4002.0)
==1272==    by 0x40FFC45: gst_tracer_record_new (gsttracerrecord.c:226)
==1272==    by 0x8049706: serialize_message_logging (gsttracerrecord.c:78)
==1272==    by 0x404FB6A: srunner_run (check_run.c:450)
==1272==    by 0x404FC22: srunner_run_all (check_run.c:674)
==1272==    by 0x4042A57: gst_check_run_suite (gstcheck.c:824)
==1272==    by 0x8048F14: main (gsttracerrecord.c:167)


structures

==408== 152 (16 direct, 136 indirect) bytes in 1 blocks are definitely lost in
loss record 1,471 of 1,499
==408==    at 0x402C17C: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==408==    by 0x423EBE2: g_malloc (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==408==    by 0x4255281: g_slice_alloc (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==408==    by 0x40EDCE1: gst_structure_new_id_empty_with_size
(gststructure.c:145)
==408==    by 0x40F020B: gst_structure_new_valist (gststructure.c:281)
==408==    by 0x40F026A: gst_structure_new (gststructure.c:253)
==408==    by 0x804968F: serialize_message_logging (gsttracerrecord.c:75)
==408==    by 0x404FB6A: srunner_run (check_run.c:450)
==408==    by 0x404FC22: srunner_run_all (check_run.c:674)
==408==    by 0x4042A57: gst_check_run_suite (gstcheck.c:824)
==408==    by 0x8048F14: main (gsttracerrecord.c:166)


str_val string

==1436== 5 bytes in 1 blocks are definitely lost in loss record 39 of 1,495
==1436==    at 0x402C17C: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==1436==    by 0x423EBE2: g_malloc (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==1436==    by 0x4256E1C: g_strdup (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==1436==    by 0x41D73C7: ??? (in
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4002.0)
==1436==    by 0x40F3189: gst_structure_get_valist (gststructure.c:3032)
==1436==    by 0x40F37A7: gst_structure_get (gststructure.c:3161)
==1436==    by 0x80492E9: serialize_static_record (gsttracerrecord.c:128)
==1436==    by 0x404FB6A: srunner_run (check_run.c:450)
==1436==    by 0x404FC22: srunner_run_all (check_run.c:674)
==1436==    by 0x4042A57: gst_check_run_suite (gstcheck.c:824)
==1436==    by 0x8048F14: main (gsttracerrecord.c:167)

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