[issue22272] sqlite3 memory leaks in cursor.execute

Changes by STINNER Victor : -- resolution: -> not a bug status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue22272] sqlite3 memory leaks in cursor.execute

A. Libotean added the comment: > Can we close this issue then? Yes, please. Sorry for the false alarm. -- ___ Python tracker ___ ___

[issue22272] sqlite3 memory leaks in cursor.execute

Ned Deily added the comment: Can we close this issue then? -- nosy: +ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue22272] sqlite3 memory leaks in cursor.execute

A. Libotean added the comment: > I'm not sure that it's a leak because it doesn't depend on the number of > queries nor the number of run of the test. It's maybe an internal sqlite > cache. You're right, the "leak" does not increase past ~300 queries executed. --

[issue22272] sqlite3 memory leaks in cursor.execute

STINNER Victor added the comment: leaking_tracemalloc.py: leaking.py adapted for tracemalloc. Output: [ Top 3 lines ] leaking_tracemalloc.py:24: size=46.0 KiB (+46.0 KiB), count=476 (+476), average=99 B leaking_tracemalloc.py:17: size=847 B (+847 B), count=6 (+6), average=141 B /home/haypo/pro

[issue22272] sqlite3 memory leaks in cursor.execute

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue22272] sqlite3 memory leaks in cursor.execute

New submission from A. Libotean: There are significant memory leaks when multiple insert statements are executed with distinct values. sqlite3 version is 2.6.0 The attached file contains two variants: * one which uses string interpolation to build the query: this generates severe leakeage *