blob: 28656e418081567cb954159793be4427ae33f76c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
|
# Full list is tracked through meta bug 793882
####################################
# Leaks in third party libraries #
####################################
{
Bug 793537
Memcheck:Leak
...
obj:/usr/lib64/libpango-1.0.so.0.2800.1
...
}
{
Bug 793598
Memcheck:Leak
...
obj:/lib64/libdbus-1.so.3.4.0
...
}
{
Bug 793600
Memcheck:Leak
fun:realloc
obj:/usr/lib64/libfontconfig.so.1.4.4
...
fun:FcDefaultSubstitute
fun:_ZN17gfxPangoFontGroup11MakeFontSetEP14_PangoLanguagedP9nsAutoRefI10_FcPatternE
...
}
# Fontconfig is going fancy with its cache structure and that confuses valgrind.
# https://bugs.freedesktop.org/show_bug.cgi?id=8215
# https://bugs.freedesktop.org/show_bug.cgi?id=8428
{
Bug 1187649
Memcheck:Leak
match-leak-kinds: definite
fun:realloc
fun:FcPatternObjectInsertElt
...
}
# With older versions of fontconfig (e.g. 2.8.0 on taskcluster systems),
# there's an uninitialized memory usage and leak when loading app fonts.
{
Bug 1231701
Memcheck:Param
write(buf)
...
fun:FcDirCacheWrite
fun:FcDirCacheScan
fun:FcConfigAddDirList
fun:FcConfigAppFontAddDir
...
}
{
Bug 1231701
Memcheck:Leak
match-leak-kinds: definite
fun:malloc
fun:FcDirScanConfig
fun:FcDirCacheScan
fun:FcConfigAddDirList
fun:FcConfigAppFontAddDir
...
}
# Leaks due to either Gtk+3 or cairo, but Gecko is not directly involved with
# those cairo interactions. One suspected cause is Gecko not closing the
# display to work around a bug in old Gtk+3 versions. See also bug 1228724.
{
Bug 1187649
Memcheck:Leak
match-leak-kinds: definite
fun:malloc
fun:_cairo_freelist_alloc
fun:_cairo_xlib_display_queue_resource
fun:_cairo_xlib_surface_finish
...
}
# The following leak is deep in Gtk+3, and it doesn't seem we're doing
# anything wrong on our end with the container objects. This suppression
# is purposefully verbose so as to avoid catching actual leaks due to
# Gecko code.
# Note: valgrind doesn't support more than 24 elements in a suppression stack.
{
Bug 1187649
Memcheck:Leak
match-leak-kinds: definite
fun:malloc
fun:g_malloc
fun:g_slice_alloc
fun:g_list_prepend
fun:gtk_combo_box_get_path_for_child
fun:gtk_container_get_path_for_child
fun:gtk_widget_get_path
fun:_gtk_widget_update_path
fun:reset_style_recurse
fun:gtk_widget_reset_style
fun:gtk_widget_set_parent
fun:gtk_combo_box_add
fun:g_cclosure_marshal_VOID__OBJECTv
fun:_g_closure_invoke_va
fun:g_signal_emit_valist
fun:g_signal_emit
fun:gtk_combo_box_constructor
fun:g_object_newv
fun:g_object_new_valist
fun:g_object_new
...
}
# set_color() in gtkstyle.c of GTK version 3.4.4 only can leak GdkRGBA
# allocations when the theme has transparent colors:
# https://git.gnome.org/browse/gtk+/tree/gtk/deprecated/gtkstyle.c?h=3.4.4#n676
{
Bug 1250704
Memcheck:Leak
match-leak-kinds: definite
fun:malloc
fun:g_malloc
fun:g_slice_alloc
fun:g_slice_copy
fun:boxed_proxy_lcopy_value
fun:gtk_style_context_get_valist
fun:gtk_style_context_get
fun:set_color
fun:gtk_style_update_from_context
fun:gtk_style_constructed
fun:g_object_newv
fun:g_object_new_valist
fun:g_object_new
...
}
{
Bug 794366
Memcheck:Leak
...
obj:/usr/lib64/libgtk-x11-2.0.so.0.1800.9
...
}
{
Bug 794368
Memcheck:Leak
...
obj:/usr/lib64/libXrandr.so.2.2.0
...
}
{
Bug 794373
Memcheck:Leak
...
obj:/lib64/libgobject-2.0.so.0.2200.5
...
}
{
Bug 966673
Memcheck:Leak
fun:malloc
obj:/lib64/libresolv-2.12.so
...
fun:gaih_inet
fun:getaddrinfo
fun:PR_GetAddrInfoByName
...
}
{
Bug 979242
Memcheck:Leak
fun:calloc
fun:xcb_connect_to_fd
fun:xcb_connect_to_display_with_auth_info
fun:_XConnectXCB
fun:XOpenDisplay
fun:gdk_display_open
...
}
###################################
# Leaks in short lived precesses #
###################################
{
Bug 984196
Memcheck:Leak
...
fun:glxtest
...
}
#########################################
# Uninitialised value false positives #
#########################################
# This concerns a false positive pertaining to Memcheck's overly-
# conservative instrumentation of CPUID. See bug 1288618 comments
# 119 through 127.
{
Bug 1288618 comments 119 through 127
Memcheck:Cond
fun:_ZN6SkOptsL4initEv
fun:sk_once_no_arg_adaptor
}
{
Bug 1288618 comments 119 through 127 part 2
Memcheck:Cond
fun:__get_cpuid
fun:cpuid
fun:_ZN6SkOptsL4initEv
fun:sk_once_no_arg_adaptor
}
|
