id summary reporter owner description type status priority milestone component version resolution keywords cc blockedby blocking branch_state votes 2828 multiple memory leaks nosebleed "==23690== 240 bytes in 1 blocks are possibly lost in loss record 81 of 135 ==23690== at 0x4C25BE5: memalign (vg_replace_malloc.c:694) ==23690== by 0x4C25C3E: posix_memalign (vg_replace_malloc.c:835) ==23690== by 0x51B99D1: slab_allocator_alloc_chunk (gslice.c:1381) ==23690== by 0x5200DA2: g_slice_alloc (gslice.c:719) ==23690== by 0x52016DD: g_slist_prepend (gslist.c:265) ==23690== by 0x52036BF: g_strsplit (gstrfuncs.c:2270) ==23690== by 0x52122F5: g_get_any_init_do (gutils.c:832) ==23690== by 0x52124F4: g_init_user_config_dir.part.0 (gutils.c:913) ==23690== by 0x5212F4C: g_get_user_config_dir (gutils.c:1296) ==23690== by 0x42A8F4: ??? (in /bin/mc) ==23690== by 0x40DE09: ??? (in /bin/mc) ==23690== by 0x5F3E12C: (below main) (libc-start.c:226) I get this multiple times. I run valgrind --leak-check=full mc . I wait to load the gui and then I exit with F10. With just those few actions I get so many memleaks. " defect closed major mc-core invalid no branch