validate: Invalid write to freed pointer on exit
@slomo
Submitted by Sebastian Dröge Link to original bug (#774744)
Description
==7736== Invalid write of size 8
==7736== at 0x6138D65: g_nullify_pointer (gutils.c:2059)
==7736== by 0x5E7AB0E: weak_refs_notify (gobject.c:2638)
==7736== by 0x5E7BC5B: g_object_unref (gobject.c:3174)
==7736== by 0x5BDD9A3: _priv_gst_tracing_deinit (gsttracerutils.c:150)
==7736== by 0x5B6133B: gst_deinit (gst.c:1036)
==7736== by 0x10ABCF: main (gst-validate.c:525)
==7736== Address 0x9d806c0 is 0 bytes inside a block of size 40 free'd
==7736== at 0x4C2BDDB: free (vg_replace_malloc.c:530)
==7736== by 0x60E7FD2: g_datalist_clear (gdataset.c:273)
==7736== by 0x5E7BC79: g_object_unref (gobject.c:3185)
==7736== by 0x10AB8D: main (gst-validate.c:515)
==7736== Block was alloc'd at
==7736== at 0x4C2ABAF: malloc (vg_replace_malloc.c:299)
==7736== by 0x6109E08: g_malloc (gmem.c:94)
==7736== by 0x6122342: g_slice_alloc (gslice.c:1025)
==7736== by 0x612296D: g_slice_alloc0 (gslice.c:1051)
==7736== by 0x51DC6A1: gst_validate_reporter_get_priv (gst-validate-reporter.c:87)
==7736== by 0x51DC84D: gst_validate_reporter_set_name (gst-validate-reporter.c:315)
==7736== by 0x5E7BE2C: object_set_property (gobject.c:1423)
==7736== by 0x5E7BE2C: g_object_constructor (gobject.c:2082)
==7736== by 0x51DDD77: gst_validate_monitor_constructor (gst-validate-monitor.c:187)
==7736== by 0x5E7C028: g_object_new_with_custom_constructor (gobject.c:1701)
==7736== by 0x5E7C028: g_object_new_internal (gobject.c:1781)
==7736== by 0x5E7E10D: g_object_new_valist (gobject.c:2042)
==7736== by 0x5E7E3B0: g_object_new (gobject.c:1626)
==7736== by 0x51E0502: gst_validate_pipeline_monitor_new (gst-validate-pipeline-monitor.c:600)