On Sep 27, 2009, at 10:32 PM, gary ng wrote:
the easiest is as you mentioned, tried to link with mysqlclient_r
and see if it works.
i've already been running it compiled w/ mysqlclient_r.
i found this documentation related to using mysqlclient_r:
"there is a special requirement by libmysqlclient_r. If you are
creating MYSQL objects in different threads the library automatically
allocates per-thread global data, but to free them you must use
mysql_thread_end()"
i tried patching the code to add mysql_thread_end() after each
mysql_close(), but it didn't seem to fix the issue. it does make me
wonder if there are other thread-related issues causing the leak when
using mysqlclient_r.
there's this whole section in the MySQL manual about making clients
thread-safe: http://dev.mysql.com/doc/refman/5.0/en/threaded-clients.html
do you guys think it's worth exploring?
otherwise, I remembered(in the rings case) that if I make a mysql
operation in the master VM(which subsequently create and destroy as
many vm that has mysql operation as the traffic goes), the leak went
away. Not sure if you can do it in freeswitch though.
yeah i don't know if i can do that, either. i'll have to check with
the devs.
_______________________________________________
Kepler-Project mailing list
Kepler-Project@lists.luaforge.net
http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
http://www.keplerproject.org/