postgresql-interfaces/psqlodbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed
From: apgrucza (@apgrucza) <[email protected]>
To: postgresql-interfaces/psqlodbc <[email protected]>
Subject: Re: [postgresql-interfaces/psqlodbc] issue #8: Memory leaks detected in psqlodbc library
Date: Sun, 28 Apr 2024 23:43:24 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

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?

view thread (31+ messages)  latest in thread

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://postgresql-interfaces/psqlodbc
  Cc: [email protected], [email protected]
  Subject: Re: [postgresql-interfaces/psqlodbc] issue #8: Memory leaks detected in psqlodbc library
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox