From: Warren Young
Date: May 11 2009 9:39pm
Subject: Re: Possible memory leak?
List-Archive: http://lists.mysql.com/plusplus/8560
Message-Id: <5BE90D05-B579-43EF-A9C6-B5D42387DA7B@etr-usa.com>
MIME-Version: 1.0 (Apple Message framework v930.3)
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On May 11, 2009, at 1:12 PM, Bruno Adami wrote:

> I found a solution. Looking trough the lists of Mysql C Api, I found  
> this topic:
>
> http://bugs.mysql.com/bug.php?id=7619

Ah.  I thought the last Connection::thread_end() call would take care  
of that.  I've updated the MySQL++ FAQ to cover this:

	http://tangentsoft.net/mysql++/#memleak

The next version of MySQL++ will have a way to avoid this leak without  
calling down into the C API directly.