On Friday, April 22, 2016 at 8:13:21 PM UTC+12, Lekare wrote: > When entering something really big, like > > :put =range(30000000000,300000000000000000000) > > Vim quits with message > > Vim: Caught deadly signal SEGV > Vim: Finished. > [1] 75479 segmentation fault \vim
On my x86-64 with 16 GiB of RAM, that causes vim to gallop through memory at about 2 GiB/s, then linux is in strife, until [ 4382.649514 ] Out of memory: Kill process 2965 (gvim) score 917 or sacrifice child [ 4382.650036 ] killed process 2965 (gvim) total-vm:30326512kB, anon-rss:15751236kB, file-rss:160kB The point I'm trying to make is that if you ask vim to do stuff beyond the resources of the system it's running on, vim will try, and the failure depends on that system. IMO it would be very difficult to code vim to reliably catch all the ways it can fail like this. Regards, John Little -- -- 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.
