Message-ID: <gh-postgresql-interfaces-psqlodbc-8-c2081701338@github.com>
From: "apgrucza (@apgrucza)" <noreply+apgrucza@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Sun, 28 Apr 2024 23:43:24 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] issue #8: Memory leaks detected in psqlodbc library
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-8@github.com>
References: <gh-postgresql-interfaces-psqlodbc-8@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: apgrucza
X-GitHub-Comment-Id: 2081701338
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 8
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/8#issuecomment-2081701338
Content-Type: text/plain; charset=utf-8

Leaks were detected in the following tests:

[11 - premature.txt](https://github.com/postgresql-interfaces/psqlodbc/files/15144184/11.-.premature.txt)
[13 - param-conversions.txt](https://github.com/postgresql-interfaces/psqlodbc/files/15144186/13.-.param-conversions.txt)
[27 - cursor-name.txt](https://github.com/postgresql-interfaces/psqlodbc/files/15144188/27.-.cursor-name.txt)
[40 - diagnostic.txt](https://github.com/postgresql-interfaces/psqlodbc/files/15144189/40.-.diagnostic.txt)
[44 - odbc-escapes.txt](https://github.com/postgresql-interfaces/psqlodbc/files/15144190/44.-.odbc-escapes.txt)
[47 - fetch-refcursors.txt](https://github.com/postgresql-interfaces/psqlodbc/files/15144192/47.-.fetch-refcursors.txt)

As you can see, mimalloc doesn't tell you where in the code the memory leaks are. Although it can integrate with memory tracking tools, the [readme](https://github.com/microsoft/mimalloc?tab=readme-ov-file#tools) recommends using the standard allocator to debug memory leaks. @progmachine are you able to provide a report from your tool whilst running the psqlODBC tests?