On Tue, March 13, 2012 22:16, Bram Moolenaar wrote: > > Christian Brabandt write: > >> On Sa, 10 Mär 2012, 驼峰 wrote: >> >> > my repro step: >> > 1. run gvim >> > 2. open NERDTree windows >> > 3. create several tabs using 't' shortcut of NERDTree plugin >> > 4. '1gt' >> > 5, maximize gvim >> > 6, '2gt' >> > 7, restore the windows size from maximize window to normal window. >> > 8, '1gt' >> > >> > Result: after 8th step, my gvim will crash definitely. >> >> Bram, I think, this patch fixes it: > > Thanks for the patch. I have been unable to reproduce the crash, I hope > someone can verify this patch fixes the problem.
I could only reproduce it on Windows. On Linux with a gtk-built version, I couldn't reproduce it either. > I do wonder how "row" can be too big, perhaps there is a problem at a > higher level? Or a sequence of events in the wrong order? I think somehow, the LineOffset array has not been updated to reflect the new screen size. > Ah, I see that Sergey has an alternative patch. Comments? Sergey probably has been using the right approach. My patch just prevents access of invalid screen lines, which prevents the crash in this case and probably doesn't hurt anyway. regards, Christian -- 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
