summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGuillaume Desmottes <guillaume.desmottes@collabora.co.uk>2015-03-23 16:07:12 +0100
committerNicolas Dufresne <nicolas.dufresne@collabora.com>2015-04-02 18:21:02 -0400
commitda5970f2c4c27be68c4442e1b3f4138c1f646388 (patch)
tree8a8655a1281fba8ae346b41ec85bb4cecf433281
parentbc76a8b6a2db1cc0605158e672b2d420b4e130d0 (diff)
gst.supp: add some closure related entries
According to desrt, closures aren't very valgrind friendly because of pointer tricks. bgo#739850 is supposed to improve the situation but for now adding a few entries to gst.supp allows me to have 0 leak reported with gst-validate. Fix https://bugzilla.gnome.org/show_bug.cgi?id=746652
-rw-r--r--gst.supp27
1 files changed, 27 insertions, 0 deletions
diff --git a/gst.supp b/gst.supp
index c08f660..c1c7731 100644
--- a/gst.supp
+++ b/gst.supp
@@ -3972,3 +3972,30 @@
timer_create(evp)
fun:timer_create@@GLIBC_2.3.3
}
+
+{
+ closures aren't valgrind friendly (bgo#739850)
+ Memcheck:Leak
+ match-leak-kinds: possible
+ fun:calloc
+ ...
+ fun:g_cclosure_new
+}
+
+{
+ closures aren't valgrind friendly (bgo#739850)
+ Memcheck:Leak
+ match-leak-kinds: possible
+ fun:malloc
+ ...
+ fun:g_closure_add_invalidate_notifier
+}
+
+{
+ closures aren't valgrind friendly (bgo#739850)
+ Memcheck:Leak
+ match-leak-kinds: possible
+ fun:calloc
+ ...
+ fun:g_closure_new_simple
+}