-
Notifications
You must be signed in to change notification settings - Fork 375
/
ruby-3.4.supp
64 lines (59 loc) · 1.41 KB
/
ruby-3.4.supp
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
# This is a valgrind suppression configuration file.
#
# We use it together with the ruby_memcheck gem to find issues in the dd-trace-rb native extensions; in some cases
# we need to ignore potential issues as they're not something we can fix (e.g. outside our code.)
#
# See https://valgrind.org/docs/manual/manual-core.html#manual-core.suppress for details.
# Ruby weak maps seem to be able to cause invalid reads?
{
ruby-weak-map
Memcheck:Addr8
fun:wmap_cmp
fun:find_table_bin_ind
fun:st_general_foreach
fun:rb_st_foreach
...
}
# When a Ruby process forks, it looks like Ruby doesn't clean up the memory of old threads?
{
ruby-native-thread-memory
Memcheck:Leak
fun:calloc
fun:calloc1
fun:rb_gc_impl_calloc
fun:native_thread_alloc
fun:native_thread_create_dedicated
fun:native_thread_create
fun:thread_create_core
...
}
# When a Ruby process forks, it looks like Ruby doesn't clean up the memory of old threads?
{
ruby-native-thread-memory-2
Memcheck:Leak
fun:calloc
fun:calloc1
fun:objspace_xcalloc
fun:ruby_xcalloc_body
fun:native_thread_alloc
fun:native_thread_create_dedicated
fun:native_thread_create
fun:thread_create_core
...
}
# We don't care about the pkg-config external tool
{
pkg-config-memory
Memcheck:Leak
...
obj:/usr/bin/pkg-config
...
}
# We don't care about the tr external tool
{
pkg-config-memory
Memcheck:Leak
...
obj:/usr/bin/tr
...
}