rzyns / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

Snapshot 70 crashes on Lion #475

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I get very frequent crashes with Snapshot 70 on 10.7.5 Intel 64.

It may be something with the YouCompleteMe plugin, because it happens when the 
autocompletion is triggered. And in the crash log there's something about 
"ins_compl_get_exp" etc. I can't confirm that...If somebody can confirm that 
it's just due to the plugin, please ignore/delete this.

The crashlog is attached to this post.

Original issue reported on code.google.com by martinfi...@gmail.com on 6 Sep 2013 at 7:24

Attachments:

GoogleCodeExporter commented 9 years ago
Please try snapshot 71, a build for OS X 10.7 should appear within the next 
couple of hours at:

https://github.com/eee19/macvim/releases

Original comment by bjorn.winckler@gmail.com on 6 Sep 2013 at 5:32

GoogleCodeExporter commented 9 years ago
I get reproducible crashes on snapshot 71, mac os 10.8.4. they are triggered 
reproducibly by 

:set ft=python

or by editing a .py file.
(i have the vim-ipython plugin installed)

Original comment by bckr...@gmail.com on 13 Sep 2013 at 11:17

GoogleCodeExporter commented 9 years ago
ps: only the currently active osx window disappears, the macvim.app keeps 
running.

Original comment by bckr...@gmail.com on 13 Sep 2013 at 11:20

GoogleCodeExporter commented 9 years ago
ok, it seems to be vim-ipythons problem. after uninstalling the vim-ipython 
bundle, no more crashes (for now)

Original comment by bckr...@gmail.com on 13 Sep 2013 at 11:24

GoogleCodeExporter commented 9 years ago
no, not only vim-ipython. without it, when editing a python file and attempting 
<C-X><C-O> completion, i get a reproducible crash as well.

Original comment by bckr...@gmail.com on 13 Sep 2013 at 11:45

GoogleCodeExporter commented 9 years ago
ok, another bit: when started from the Terminal, i get 

"ImportError: No module named site"

upon the crash. looks like some python version mismatch. i have anaconda's 
python in my path before the system python but this has not been a problem for 
vim before.

Original comment by bckr...@gmail.com on 13 Sep 2013 at 11:50