For many months I have noticed a bug whereby a sort results in corrupted text. I've been using a rather outdated Vim and the conditions for the corruption are not reproducible. I have recently upgraded to Vim 7.4.972 and just saw the bug again. I'm running 32-bit Vim with gigabytes of memory.
Here is an outline of what sometimes shows the corruption. - Edit a big file (say 150 MB with two million lines). - Copy some of the file (say 20,000 lines) to another buffer. - Edit the copied text including some complex :s commands. - Enter :sort to sort the result. - Repeat last two steps a few times, possibly in other buffers. The big file activates plugin/LargeFile.vim which is the original Mar 30, 2006 release on my system. It just changes some settings so should not be relevant. The result often works, but sometimes it is corrupted. The result is the correct number of lines, but most of them are empty. Lines that aren't empty contain snippets of the old text (for example, one line was the last three characters of a twenty-character line in the original). This is a pretty useless report because whenever I've tried to reproduce the problem I fail. Is anyone else seeing this? Does anyone have a stress testing system? John -- -- 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/d/optout.
