__gc metamethod not running for mysql statement handles causes memory leak

[GoogleCodeExporter]

__gc metamethod not running for mysql statement handles causes memory leak

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

sorry for the bad intel, the __gc metamethod is running, the leak is caused by
something else, here's a test case:

local sth = dbh:prepare[[ SELECT 1 + ? ]]
local i = 0
while true do
   i = i + 1
   sth:execute(i)
   local row = sth:fetch()
end

calling :execute(...) multiple times on a statement handle is leaky somehow

Original comment by [email protected] on 21 Apr 2010 at 5:49

[GoogleCodeExporter]

solved this now, just need a:

+    if (statement->metadata) {
+        mysql_free_result(statement->metadata);
+    }

luadbi-read-only/dbd/mysql/statement.c near the top of:
static int statement_execute(lua_State *L)

I'd send a patch with this and a couple of other fixes in it to the mysql 
driver if
you let me know where to send it

Original comment by [email protected] on 21 Apr 2010 at 6:18

[GoogleCodeExporter]

Thanks for the patch! I'll apply it to trunk ASAP.

Original comment by [email protected] on 12 May 2010 at 1:53

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by [email protected] on 16 Jul 2010 at 6:28

• Changed state: Fixed