leak using gthreads?


Valgrind reports the following "possible" leak while using gthreads (tested with glib-2.16.5 and 2.16.6, and I can't see any related changes in cvs). The value of 16,688 bytes reported by valgrind seems to increase linearly with programme execution time.

Is this unexpected behaviour or just a false alarm due to glib's memory allocation mechanisms?


==2255== 16,688 bytes in 26 blocks are possibly lost in loss record 34 of 36
==2255==    at 0x4021A92: memalign (vg_replace_malloc.c:460)
==2255==    by 0x4021B3F: posix_memalign (vg_replace_malloc.c:569)
==2255==    by 0x4E6C0B3: slab_allocator_alloc_chunk (gslice.c:1136)
==2255==    by 0x4E6D2E0: g_slice_alloc (gslice.c:666)
==2255==    by 0x4E2A3DE: g_array_sized_new (garray.c:86
==2255==    by 0x4E2A4E6: g_array_new (garray.c:78)
==2255==    by 0x4E783E0: g_static_private_set (gthread.c:451)
==2255==    by 0x4E39B0F: g_get_filename_charsets (gconvert.c:1185)
==2255==    by 0x4E39B80: _g_convert_thread_init (gconvert.c:1290)
==2255==    by 0x4E78699: g_thread_init_glib (gthread.c:165)
==2255==    by 0x4EEA576: g_thread_init (gthread-impl.c:355)
==2255==    by 0x806ADA3: main (heart.c:120)

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]