Message-ID: <gh-postgresql-interfaces-psqlodbc-47-c2377252069@github.com>
From: "siga0984 (@siga0984)" <noreply+siga0984@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Thu, 26 Sep 2024 15:10:59 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] issue #47: Memory Corruption using version 16.00.0005
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-47@github.com>
References: <gh-postgresql-interfaces-psqlodbc-47@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: siga0984
X-GitHub-Comment-Id: 2377252069
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 47
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/47#issuecomment-2377252069
Content-Type: text/plain; charset=utf-8

> Spent entire evening yesterday investigating problem. Found only one place where refcnt can broke. Also found one place where COL_INFO objects may leak. In a minute i'll prepare pull request for this. It will be fine if @siga0984 can test this fix and confirm if bug is gone away.

Yes, I can !! 👍 Just let me know where i can download a beta / release candidate psqlodbc30a.dll to test !!