valgrind reports the following memory leak:

 ==7627== 16,384 bytes in 1 blocks are definitely lost in loss record 4,210 of 4,215
| ==7627==    at 0x4C2AC4F: malloc (vg_replace_malloc.c:299)
| ==7627==    by 0x8DA5008: g_malloc (in /home/patricia/products/unittest/builds/tmp/sysroots/x86_64-linux/usr/lib/libglib-2.0.so.0.4600.2)
| ==7627==    by 0x8DAEEBB: g_quark_init (in /home/patricia/products/unittest/builds/tmp/sysroots/x86_64-linux/usr/lib/libglib-2.0.so.0.4600.2)
| ==7627==    by 0x8D71B88: glib_init_ctor (in /home/patricia/products/unittest/builds/tmp/sysroots/x86_64-linux/usr/lib/libglib-2.0.so.0.4600.2)
| ==7627==    by 0x400F5D9: call_init.part.0 (in /lib/x86_64-linux-gnu/ld-2.24.so)
| ==7627==    by 0x400F6EA: _dl_init (in /lib/x86_64-linux-gnu/ld-2.24.so)
| ==7627==    by 0x4000CD9: ??? (in /lib/x86_64-linux-gnu/ld-2.24.so)
| ==7627==


Adding a new suppression solves the problem:

{
   <insert_a_suppression_name_here>
   Memcheck:Leak
   match-leak-kinds: definite
   fun:malloc
   fun:g_malloc
   fun:g_quark_init
   fun:glib_init_ctor
   fun:call_init.part.0
   fun:_dl_init
   obj:*/ld-*.so
}