On Fri, Nov 26, 2021 at 01:03:40PM +0100, Dominik Vogt wrote:
> Stuck with this one, ideas welcome:
>
> On Wed, Nov 24, 2021 at 03:22:54PM +0100, Dominik Vogt wrote:
> > ==8482== 38 (16 direct, 22 indirect) bytes in 1 blocks are definitely lost
> > in loss record 184 of 536
> > ==8482==at
Stuck with this one, ideas welcome:
On Wed, Nov 24, 2021 at 03:22:54PM +0100, Dominik Vogt wrote:
> ==8482== 38 (16 direct, 22 indirect) bytes in 1 blocks are definitely lost in
> loss record 184 of 536
> ==8482==at 0x48386AF: malloc (in
>
I can't figure out when this memory is leaked:
==8482== 21 bytes in 1 blocks are definitely lost in loss record 155 of 536
==8482==at 0x483877F: malloc (in
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==8482==by 0x5FE76A7: __vasprintf_internal (vasprintf.c:71)
