You are not logged in.
Pages: 1
Hi all,
My GVim (installed from the Arch repos) has recently become very unstable, easily segfaulting every couple of minutes.
I do use a fairly large number of plugins (see below) and I could try disactivating them one at a time to see if one of them is the culprit but I'd rather not go though that route, so has anyone had this kind of problem before?
Thanks in advance.
Bundle 'AnsiEsc.vim'
Bundle 'calendar.vim'
Bundle 'Color-Sampler-Pack'
Bundle 'colorsupport.vim'
Bundle 'easytags.vim'
Bundle 'echofunc.vim'
Bundle 'sjl/gundo.vim'
Bundle 'Indent-Guides'
Bundle 'indentpython.vim'
Bundle 'LargeFile'
Bundle 'LaTeX-Box'
Bundle 'number-marks'
Bundle 'matchit.zip'
Bundle 'MatlabFilesEdition'
Bundle 'mlint.vim--Ibbotson'
Bundle 'mru.vim'
Bundle 'perl.vim'
Bundle 'Python-Syntax-Folding'
Bundle 'quickfixsigns'
Bundle 'recover.vim'
Bundle 'repeat.vim'
Bundle 'Screen-vim---gnu-screentmux'
Bundle 'sherlock.vim'
Bundle 'snipMate'
Bundle 'spacehi.vim'
Bundle 'surround.vim'
Bundle 'SuperTab-continued.'
Bundle 'tabpagecolorscheme'
Bundle 'Tagbar'
Bundle 'tex.vim--Tanzler'
Bundle 'The-NERD-Commenter'
Bundle 'The-NERD-tree'
Bundle 'VimClojure'
Bundle 'vim-ipython'
Bundle 'VimOutliner'
Bundle 'vimoutliner-colorscheme-fix'
Bundle 'gmarik/vundle'
Bundle 'othree/xml.vim'
Bundle 'YankRing.vimOffline
I use vim from a shell so i cant offer anything on gvim. Any other system instabilities? In other words, could it be a hardware issue like bad memory?
Offline
There is a bug reported where the :python causes segfault, there is a discussion on it on the vim mailing list. It might be what is causing it if one of your plugins uses :python
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
Actually vim crashes in the same fashion... I'm using emacs with evil mode right now as a backup but I'm far from having reached my previous level of customization, and that sucks :-)
My computer works fine other than that, so I don't think it's a hardware issue.
On the other hand, I noticed that when this instability started, I would get "deadly signal segv caught" printed to my terminal after the crash, but now sometimes I don't even get that line anymore.
Offline
Downgraded back to 475 as mentioned in the other thread, works fine now.
Offline
Pages: 1