Message-ID: <gh-postgresql-interfaces-psqlodbc-8-c2112811456@github.com>
From: "progmachine (@progmachine)" <noreply+progmachine@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Wed, 15 May 2024 15:07:06 +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: progmachine
X-GitHub-Comment-Id: 2112811456
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-2112811456
Content-Type: text/plain; charset=utf-8

> It might be interesting to run the leak test with destroy set to true always to confirm

It's dangerous, because somewhere else will be dangling pointers. As a minimum, i know that StatementClass objects have same pointers, and if you always delete these objects, then use after free situations are possible.