It's invalid because the posted code snippet doesn't contain a call to Connection::thread_end() and to mysql_library_end(), as the referenced MySQL++ FAQ item tells you to. Since that is the advice given to plug memory leaks and the complaint is about memory leaks, I don't see that this is a valid bug report.

If you think you have something valid, you have to provide a test case that doesn't itself have known problems.

I am sorry, i am haste.

My sustem is: Linux gz 2.6.35-25-generic #44-Ubuntu
I compiled main.cpp (in attachment) file using gcc 4.4:
{{{
g++ main.cpp -I /usr/include/mysql -lmysqlpp
}}}

and ran it under valgrind-3.6.0
{{{
valgrind --leak-check=full ./a.out
}}}

I got (full text in attachment: before.txt):
{{{
==8453== LEAK SUMMARY:
==8453== definitely lost: 104,544 bytes in 99 blocks
==8453== indirectly lost: 106,688 bytes in 394 blocks
==8453== possibly lost: 3,168 bytes in 7 blocks
==8453== still reachable: 16 bytes in 1 blocks
==8453== suppressed: 0 bytes in 0 blocks
}}}

I used another patch without using tr1 (in attachment: patch.diff)
and got (after.txt):
{{{
==8740== LEAK SUMMARY:
==8740== definitely lost: 0 bytes in 0 blocks
==8740== indirectly lost: 0 bytes in 0 blocks
==8740== possibly lost: 0 bytes in 0 blocks
==8740== still reachable: 16 bytes in 1 blocks
==8740== suppressed: 0 bytes in 0 blocks
}}}

Sorry if i blind and missed something.

(file #12486, file #12487, file #12488, file #12489)

How to repeat:
int main()
{
while (true)
{
try
{
mysqlpp::Connection conn("Config", "127.2.3.4", "user", "123", 123);
}
catch (...) { }
}
}

To fix i used:

Index: connection.cpp
===================================================================
--- connection.cpp (revision 2685)
+++ connection.cpp (working copy)
@@ -64,7 +64,6 @@
Connection::~Connection()
{
disconnect();
- delete driver_;
}

Index: connection.h
===================================================================
--- connection.h (revision 2685)
+++ connection.h (working copy)
@@ -41,6 +41,7 @@
#include "options.h"

#include <string>
+#include <tr1/memory>

namespace mysqlpp {

@@ -164,7 +165,7 @@
/// the mailing list asking about it. Unless you're doing something
/// very low-level, there should never be a reason to use the
/// driver directly.
- DBDriver* driver() { return driver_; }
+ DBDriver* driver() { return driver_.get(); }

/// \brief Asks the database server to drop (destroy) a database
///
@@ -352,7 +353,7 @@
mutable std::string error_message_; ///< MySQL++ specific error, if
any

private:
- DBDriver* driver_;
+ std::tr1::shared_ptr<DBDriver> driver_;
bool copacetic_;
};