--- On Mon, 3/15/10, Chad Phillips -- Apartment Lines <c...@apartmentlines.com> wrote: > i'm pretty sure the reason this appears so badly with > FreeSWITCH is because the FreeSWITCH master process uses a > new instance of Lua any time it gets a call to run a Lua > script. since the master FreeSWITCH process runs > continuously, the memory leak builds up. i'm guessing > for most use cases, the Lua script leveraging LuaSQL is > called directly and then the process terminates, so the leak > never builds up. I reported this problem long ago for the ring usage of lua in Kepler. My conclusion back then was, either use cgilua(i.e. as you mentioned one process per request) or use one lua process without ring and use Lua's function table to isolate requests. Both solution worked for me so I no longer pursuit on the proper solution for the mysql client issue.
_______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
