On Thu, Apr 11, 2013 at 6:07 AM, Bram Moolenaar <[email protected]> wrote:
> > Yasuhiro Matsumoto wrote: > > > lua is managing vim objects in cache table to release with finalizer. > > So it doesn't need to call something in luaV_dict_gc/luaV_list_gc to > > undef vim objects. it makes double free. > > Thanks for the quick response! > > I have a note in the todo list that test 85, when run with valgrind, > finds memory leaks in Lua. Did you every run with Lua under valgrind? > I found a few memory leaks in if_lua.c. Please check the attached patch. -- Yukihiro Nakadaira - [email protected] -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
iflualeak.diff
Description: Binary data
