Hi, Bram, Thanks for your reply. Actually, I am working in Windows and don't have valgrind.
The crash can be easily reproed by using two plugins: NERDTree and buf_it. Their links are: http://www.vim.org/scripts/script.php?script_id=1658 http://www.vim.org/scripts/script.php?script_id=2833 The repro step is: 1. open a nerdtree window by using NERDTree. 2. in the NERDTree window, hit "t" key to create several tabs. 3. switch to other tabs by using "2gt" or click the tab button. Then you will hit crash definitely. After some investigation, I found the crash is hit by the command "redraw" in buf_it.vim. If i comment out the redraw in that file. gvim won't crash. Here are some clauses related to redraw. autocmd VimEnter,BufNew,BufEnter,BufWritePost,VimResized * call UpdateStatus() function! UpdateStatus() blablabla blablabla blablabla ... ... redraw endfunction Another easy repro step is adding the following line in vimrc configuration file and install NERDTree. autocmd VimEnter,BufNew,BufEnter,BufWritePost,VimResized * redraw Thanks, -Mike Guo > > Don't see something special here. > > Can you run Vim with valgrind, then we can see what happens with > allocated memory early. See ":help valgrind". > > -- > If you feel lonely, try schizophrenia. > > /// Bram Moolenaar -- [email protected] --http://www.Moolenaar.net \\\ > /// sponsor Vim, vote for features --http://www.Vim.org/sponsor/\\\ > \\\ an exciting new programming language --http://www.Zimbu.org /// > \\\ help me help AIDS victims --http://ICCF-Holland.org /// -- 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
