On 10/7/07, Tony Mechelynck <[EMAIL PROTECTED]> wrote: > > It's not clear to me what memory is leaked (if any is really leaked, > > valgrind may give a false warning). When I put this line before "syntax > > on" it appears to disappear: > > > > let g:vimembedscript= 0 > > > > So it's related to ":syn include". > > > > What this setting changes is that it forbids sourcing of syntax/perl.vim, > syntax/python.vim, syntax/tcl.vim, syntax/ruby.vim and syntax/scheme.vim from > within syntax/vim.vim so maybe you (Dominique) might want to investigate which > one(s) of them leak(s) memory. (Rename one or more of them to something else, > or move them elsewhere -- temporarily of course -- and see if the leak > persists.) > > Best regards, > Tony.
I can confirm that I also don't see the leak anymore when I add "let g:vimembedscript= 0" in the "leak.vim" script. Following the good advice of Tony, by trial and error, i.e. commenting pieces of /usr/local/share/vim/vim71/syntax/vim.vim, I found this: - comment out all of ruby python tcl mzscheme ---> no leak - enable perl syntax only -----------------------> no leak - enable ruby syntax only -----------------------> ***LEAK!*** - enable python syntax only ---------------------> no leak - enable tcl syntax only ------------------------> no leak - enable mzscheme syntax only -------------------> no leak So the leak (assuming it's not spurious) comes somehow from ruby.vim only. I will try to narrow down further in ruby.vim later when I have time. -- Dominique --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
