https://bugs.kde.org/show_bug.cgi?id=358980
--- Comment #14 from Paul Floyd <pjfl...@wanadoo.fr> --- On Arch I get ==16682== HEAP SUMMARY: ==16682== in use at exit: 24,879 bytes in 29 blocks ==16682== total heap usage: 335 allocs, 306 frees, 233,296 bytes allocated ==16682== ==16682== 8 bytes in 1 blocks are definitely lost in loss record 1 of 15 ==16682== at 0x48447C2: malloc (vg_replace_malloc.c:446) ==16682== by 0x96A0A35: ??? ==16682== by 0x96B788F: ??? ==16682== by 0x969F1BB: ??? ==16682== by 0x40045B6: call_init (dl-init.c:74) ==16682== by 0x40045B6: call_init (dl-init.c:26) ==16682== by 0x40046AC: _dl_init (dl-init.c:121) ==16682== by 0x40015C1: _dl_catch_exception (dl-catch.c:215) ==16682== by 0x400B4FB: dl_open_worker (dl-open.c:829) ==16682== by 0x4001522: _dl_catch_exception (dl-catch.c:241) ==16682== by 0x400B903: _dl_open (dl-open.c:905) ==16682== by 0x4CA3F13: dlopen_doit (dlopen.c:56) ==16682== by 0x4001522: _dl_catch_exception (dl-catch.c:241) ==16682== ==16682== 96 bytes in 1 blocks are definitely lost in loss record 10 of 15 ==16682== at 0x484BEFF: calloc (vg_replace_malloc.c:1675) ==16682== by 0x96A0A6D: ??? ==16682== by 0x969F100: ??? ==16682== by 0x969F1D7: ??? ==16682== by 0x40045B6: call_init (dl-init.c:74) ==16682== by 0x40045B6: call_init (dl-init.c:26) ==16682== by 0x40046AC: _dl_init (dl-init.c:121) ==16682== by 0x40015C1: _dl_catch_exception (dl-catch.c:215) ==16682== by 0x400B4FB: dl_open_worker (dl-open.c:829) ==16682== by 0x4001522: _dl_catch_exception (dl-catch.c:241) ==16682== by 0x400B903: _dl_open (dl-open.c:905) ==16682== by 0x4CA3F13: dlopen_doit (dlopen.c:56) ==16682== by 0x4001522: _dl_catch_exception (dl-catch.c:241) ==16682== ==16682== LEAK SUMMARY: ==16682== definitely lost: 104 bytes in 2 blocks ==16682== indirectly lost: 0 bytes in 0 blocks ==16682== possibly lost: 0 bytes in 0 blocks ==16682== still reachable: 24,775 bytes in 27 blocks ==16682== suppressed: 0 bytes in 0 blocks ==16682== Reachable blocks (those to which a pointer was found) are not shown. ==16682== To see them, rerun with: --leak-check=full --show-leak-kinds=all I'll open a glibc item for that. -- You are receiving this mail because: You are watching all bug changes.
