Closed claucece closed 6 years ago
Hey @natalieesk , I saw you referencing this issue. Are you working on it? If so, can you assign it to you here? it's just for clarity.. thanks! :)
This may have been fixed by the completion of #13. If no more flaky mem leaks occur in this next week, we can close this issue.
As found by @tuliocasagrande , these mem leaks still show up:
==26999== 16 bytes in 1 blocks are possibly lost in loss record 193 of 421
==26999== at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26999== by 0x51555DC: ??? (in /usr/lib/x86_64-linux-gnu/libotr.so.5.1.1)
==26999== by 0x57F9069: do_malloc (global.c:912)
==26999== by 0x57FA7F1: _gcry_malloc_secure_core (global.c:946)
==26999== by 0x57FA7F1: _gcry_xmalloc_secure (global.c:1145)
==26999== by 0x57FA8C6: _gcry_xcalloc_secure (global.c:1190)
==26999== by 0x58BE314: _gcry_mpi_resize (mpiutil.c:187)
==26999== by 0x58BC0EF: mpi_fromstr (mpicoder.c:134)
==26999== by 0x58BC0EF: _gcry_mpi_scan (mpicoder.c:602)
==26999== by 0x57F6448: gcry_mpi_scan (visibility.c:357)
==26999== by 0x42A483: dh_init (dh.c:63)
==26999== by 0x40AB6E: test_api_multiple_clients (test_api.c:644)
==26999== by 0x4EA97DA: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA99A2: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999==
==26999== 32 bytes in 1 blocks are possibly lost in loss record 280 of 421
==26999== at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26999== by 0x51555DC: ??? (in /usr/lib/x86_64-linux-gnu/libotr.so.5.1.1)
==26999== by 0x57F9069: do_malloc (global.c:912)
==26999== by 0x57FA6CB: _gcry_malloc (global.c:936)
==26999== by 0x57FA6CB: _gcry_xmalloc (global.c:1110)
==26999== by 0x58BE1F1: _gcry_mpi_alloc_secure (mpiutil.c:105)
==26999== by 0x58BBBB4: _gcry_mpi_scan (mpicoder.c:601)
==26999== by 0x57F6448: gcry_mpi_scan (visibility.c:357)
==26999== by 0x42A43B: dh_init (dh.c:57)
==26999== by 0x40AB6E: test_api_multiple_clients (test_api.c:644)
==26999== by 0x4EA97DA: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA99A2: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA9BAD: g_test_run_suite (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999==
==26999== 32 bytes in 1 blocks are possibly lost in loss record 281 of 421
==26999== at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26999== by 0x51555DC: ??? (in /usr/lib/x86_64-linux-gnu/libotr.so.5.1.1)
==26999== by 0x57F9069: do_malloc (global.c:912)
==26999== by 0x57FA6CB: _gcry_malloc (global.c:936)
==26999== by 0x57FA6CB: _gcry_xmalloc (global.c:1110)
==26999== by 0x58BE1F1: _gcry_mpi_alloc_secure (mpiutil.c:105)
==26999== by 0x58BBBB4: _gcry_mpi_scan (mpicoder.c:601)
==26999== by 0x57F6448: gcry_mpi_scan (visibility.c:357)
==26999== by 0x42A45F: dh_init (dh.c:60)
==26999== by 0x40AB6E: test_api_multiple_clients (test_api.c:644)
==26999== by 0x4EA97DA: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA99A2: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA9BAD: g_test_run_suite (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999==
==26999== 32 bytes in 1 blocks are possibly lost in loss record 282 of 421
==26999== at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26999== by 0x51555DC: ??? (in /usr/lib/x86_64-linux-gnu/libotr.so.5.1.1)
==26999== by 0x57F9069: do_malloc (global.c:912)
==26999== by 0x57FA6CB: _gcry_malloc (global.c:936)
==26999== by 0x57FA6CB: _gcry_xmalloc (global.c:1110)
==26999== by 0x58BE1F1: _gcry_mpi_alloc_secure (mpiutil.c:105)
==26999== by 0x58BBBB4: _gcry_mpi_scan (mpicoder.c:601)
==26999== by 0x57F6448: gcry_mpi_scan (visibility.c:357)
==26999== by 0x42A483: dh_init (dh.c:63)
==26999== by 0x40AB6E: test_api_multiple_clients (test_api.c:644)
==26999== by 0x4EA97DA: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA99A2: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA9BAD: g_test_run_suite (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999==
==26999== 392 bytes in 1 blocks are possibly lost in loss record 407 of 421
==26999== at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26999== by 0x51555DC: ??? (in /usr/lib/x86_64-linux-gnu/libotr.so.5.1.1)
==26999== by 0x57F9069: do_malloc (global.c:912)
==26999== by 0x57FA7F1: _gcry_malloc_secure_core (global.c:946)
==26999== by 0x57FA7F1: _gcry_xmalloc_secure (global.c:1145)
==26999== by 0x57FA8C6: _gcry_xcalloc_secure (global.c:1190)
==26999== by 0x58BE314: _gcry_mpi_resize (mpiutil.c:187)
==26999== by 0x58BC0EF: mpi_fromstr (mpicoder.c:134)
==26999== by 0x58BC0EF: _gcry_mpi_scan (mpicoder.c:602)
==26999== by 0x57F6448: gcry_mpi_scan (visibility.c:357)
==26999== by 0x42A43B: dh_init (dh.c:57)
==26999== by 0x40AB6E: test_api_multiple_clients (test_api.c:644)
==26999== by 0x4EA97DA: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA99A2: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999==
==26999== 392 bytes in 1 blocks are possibly lost in loss record 408 of 421
==26999== at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26999== by 0x51555DC: ??? (in /usr/lib/x86_64-linux-gnu/libotr.so.5.1.1)
==26999== by 0x57F9069: do_malloc (global.c:912)
==26999== by 0x57FA7F1: _gcry_malloc_secure_core (global.c:946)
==26999== by 0x57FA7F1: _gcry_xmalloc_secure (global.c:1145)
==26999== by 0x57FA8C6: _gcry_xcalloc_secure (global.c:1190)
==26999== by 0x58BE314: _gcry_mpi_resize (mpiutil.c:187)
==26999== by 0x58BC0EF: mpi_fromstr (mpicoder.c:134)
==26999== by 0x58BC0EF: _gcry_mpi_scan (mpicoder.c:602)
==26999== by 0x57F6448: gcry_mpi_scan (visibility.c:357)
==26999== by 0x42A45F: dh_init (dh.c:60)
==26999== by 0x40AB6E: test_api_multiple_clients (test_api.c:644)
==26999== by 0x4EA97DA: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA99A2: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999==
==26999== 400 bytes in 1 blocks are possibly lost in loss record 409 of 421
==26999== at 0x4C2FD5F: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26999== by 0x5155664: ??? (in /usr/lib/x86_64-linux-gnu/libotr.so.5.1.1)
==26999== by 0x57FA4A2: _gcry_realloc_core (global.c:998)
==26999== by 0x57FA764: _gcry_xrealloc (global.c:1127)
==26999== by 0x58BE336: _gcry_mpi_resize (mpiutil.c:179)
==26999== by 0x58B7C69: _gcry_mpi_sub_ui (mpi-add.c:178)
==26999== by 0x42A4B2: dh_init (dh.c:67)
==26999== by 0x40AB6E: test_api_multiple_clients (test_api.c:644)
==26999== by 0x4EA97DA: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA99A2: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA9BAD: g_test_run_suite (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==26999== by 0x4EA9BD0: g_test_run (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
Close as we are tracking over #81
Currently, there seems to be three memory leaks (that show up randomly on ci):