Any hint will help me to identify root cause of leak. Thanks
On Mon, Mar 10, 2014 at 2:58 PM, techi eth <[email protected]> wrote: > Hi, > > I come across memory leak with sqlite3 online backup api (Leak detected by > valgrind tool). I have used reference code from below link for test. > (Online backup for running database) > > http://www.sqlite.org/backup.html > > Please find below memory leak snapshot for reference. > > ==6084== 78,688 (880 direct, 77,808 indirect) bytes in 1 blocks are > definitely lost in loss record 52 of 52 > ==6084== at 0x4C2B6CD: malloc (in > /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) > ==6084== by 0x571C73E: ??? (in > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6) > ==6084== by 0x56FA238: ??? (in > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6) > ==6084== by 0x5701B17: ??? (in > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6) > ==6084== by 0x5701B44: ??? (in > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6) > ==6084== by 0x576FB91: ??? (in > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6) > ==6084== by 0x4E36001: db_sqlite3_backup (db_sqlite3.c:2291) > ==6084== by 0x4026A7: Test_backup (db_sqlite3_test.c:994) > ==6084== by 0x40283D: main (db_sqlite3_test.c:1170) > ==6084== > ==6084== LEAK SUMMARY: > ==6084== definitely lost: 880 bytes in 1 blocks > > Thanks > > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
