Closed Robert-M-Muench closed 7 years ago
Using Snapshot 116 works. I suspect this has to do with the Python detection. I'm using the macports Pyhton version or the Apple stock one.
Could you share the crashlog under ~/Library/Logs/DiagnosticReports
?
Here's mine from yesterday. I don't know when or how it crashed but I always have MacVim up (I'm a writer and just a rank amateur programmer) and then suddenly it wasn't there.
Process: Vim [44488] Path: /usr/local/Cellar/macvim/8.0-117/MacVim.app/Contents/MacOS/Vim Identifier: Vim Version: 0 Code Type: X86-64 (Native) Parent Process: MacVim [43456] Responsible: Vim [44488] User ID: 501
Date/Time: 2016-12-05 06:08:14.925 -0700 OS Version: Mac OS X 10.12.1 (16B2555) Report Version: 12 Anonymous UUID: 9356ACE0-2C10-6355-9180-ED10E929CF93
Sleep/Wake UUID: 1C622883-5975-40B6-A2DE-1A1956F34CE5
Time Awake Since Boot: 320000 seconds Time Since Wake: 2600 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: Vim [44488]
VM Regions Near 0: --> __TEXT 0000000107103000-00000001072e4000 [ 1924K] r-x/rwx SM=COW /usr/local/Cellar/macvim/8.0-117/MacVim.app/Contents/MacOS/Vim
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fffd881c716 __kill + 10 1 Vim 0x00000001071e80b3 mch_exit + 184 2 Vim 0x00000001072b2c8c getout + 543 3 libsystem_platform.dylib 0x00007fffd88fbbba _sigtramp + 26 4 ??? 000000000000000000 0 + 0 5 libruby.2.0.0.dylib 0x00000001077580a2 0x10772d000 + 176290 6 libruby.2.0.0.dylib 0x0000000107757f7b rb_bug + 180 7 libruby.2.0.0.dylib 0x0000000107775a4c rb_update_max_fd + 56 8 libruby.2.0.0.dylib 0x0000000107778fc2 0x10772d000 + 311234 9 libruby.2.0.0.dylib 0x000000010777ebab 0x10772d000 + 334763 10 libruby.2.0.0.dylib 0x000000010777a55d Init_IO + 3356 11 libruby.2.0.0.dylib 0x00000001077759b2 rb_call_inits + 129 12 libruby.2.0.0.dylib 0x000000010775bf34 ruby_setup + 127 13 libruby.2.0.0.dylib 0x000000010775bf6e ruby_init + 9 14 Vim 0x00000001072a083b ensure_ruby_initialized + 62 15 Vim 0x00000001072a07c2 ex_ruby + 36 16 Vim 0x0000000107158a70 do_cmdline + 6287 17 Vim 0x0000000107155fb5 do_source + 1608 18 Vim 0x00000001072b1b23 vim_main2 + 426 19 Vim 0x00000001072b1285 main + 6957 20 libdyld.dylib 0x00007fffd86ee255 start + 1
Thread 1: 0 libsystem_kernel.dylib 0x00007fffd881d4e6 __workq_kernreturn
Thread 2: 0 libsystem_kernel.dylib 0x00007fffd881d4e6 __workq_kernreturn
Thread 3: 0 libsystem_kernel.dylib 0x00007fffd881d4e6 __workq_kernreturn
Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x00000001073138a4 rcx: 0x000000010798aa28 rdx: 0x0000000000000000 rdi: 0x000000000000adc8 rsi: 0x000000000000000b rbp: 0x000000010798aa50 rsp: 0x000000010798aa28 r8: 0x00000000fffffffd r9: 0x00007f969780e400 r10: 0x00000001071eb39c r11: 0x0000000000000206 r12: 0x000000010798aa68 r13: 0x0000000107313678 r14: 0x0000000000000001 r15: 0x0000000107313678 rip: 0x00007fffd881c716 rfl: 0x0000000000000206 cr2: 0x00000001072b9eb4
Logical CPU: 0 Error Code: 0x02000025 Trap Number: 133
Binary Images: 0x107103000 - 0x1072e3ff7 +Vim (0)
@RichardDooling snapshot-116 works fine for you?
I used 116 from the time it came out until 117 came out and never had an issue. I use MacVim all day every day, installed by brew.
Thanks
Rick
On Tue, Dec 6, 2016 at 10:49 AM, Kazuki Sakamoto notifications@github.com wrote:
@RichardDooling https://github.com/RichardDooling snapshot-116 works fine for you?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/macvim-dev/macvim/issues/432#issuecomment-265220376, or mute the thread https://github.com/notifications/unsubscribe-auth/ABaFwsSo7dEio27tRUbV2-EOy-NmEmUJks5rFaAxgaJpZM4LFVoY .
--
rd
I'll keep using 117 and let you know if anything else happens.
Thanks again
Rick
On Tue, Dec 6, 2016 at 10:54 AM, Richard Dooling rpdooling@gmail.com wrote:
I used 116 from the time it came out until 117 came out and never had an issue. I use MacVim all day every day, installed by brew.
Thanks
Rick
On Tue, Dec 6, 2016 at 10:49 AM, Kazuki Sakamoto <notifications@github.com
wrote:
@RichardDooling https://github.com/RichardDooling snapshot-116 works fine for you?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/macvim-dev/macvim/issues/432#issuecomment-265220376, or mute the thread https://github.com/notifications/unsubscribe-auth/ABaFwsSo7dEio27tRUbV2-EOy-NmEmUJks5rFaAxgaJpZM4LFVoY .
--
rd
--
rd
Can you guys try snapshot-118? https://github.com/macvim-dev/macvim/releases/tag/snapshot-118 I'm not so sure it will fix your case since I didn't get the crashlog from @Robert-M-Muench
Sure I will try it. But let me know if there's a command I should run to test it or something, because I have no idea how mine happened. It just shut itself down, which it never does.
Thanks a lot.
Rick
On Wed, Dec 7, 2016 at 4:53 PM, Kazuki Sakamoto notifications@github.com wrote:
Can you guys try snapshot-118? https://github.com/macvim-dev/ macvim/releases/tag/snapshot-118 I'm not so sure it will fix your case since I didn't get the crashlog from @Robert-M-Muench https://github.com/Robert-M-Muench
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/macvim-dev/macvim/issues/432#issuecomment-265611466, or mute the thread https://github.com/notifications/unsubscribe-auth/ABaFwuNPagBdyhYLRdu_UN0gDcQpX-KCks5rF0cMgaJpZM4LFVoY .
--
rd
@RichardDooling just use MacVim as usual is enough
snapshot-119 should be fine if the crash was came from Python 3. https://github.com/macvim-dev/macvim/releases/tag/snapshot-119
Sorry, for the delay I was not available... snapshot-119 seems to work for me now.
Anyway, please find all the crash-logs attached to have an other case for cross-checking the 119 fix.
@Robert-M-Muench thanks, I can confirm the cause of the crash.
Since the last two updates, now using Custom Version 8.0 (117), macvim crashes immediately when I press a key like I or O to start editing a file.
I'm using VimBox. Everything worked perfect before.
:version VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Dec 1 2016 06:20:27) MacOS X (unix) version Included patches: 1-106 Compiled by travis@Traviss-Mac-592.local Huge version with MacVim GUI. Features included (+) or not (-): +acl +clientserver +cursorbind +ex_extra +fullscreen +langmap +modify_fname +mouse_urxvt +path_extra +reltime +syntax +timers +viminfo -xpm +arabic +clipboard +cursorshape +extra_search -gettext +libcall +mouse +mouse_xterm +perl/dyn +rightleft +tag_binary +title +vreplace -xsmp +autocmd +cmdline_compl +dialog_con_gui +farsi -hangul_input +linebreak +mouseshape +multi_byte +persistent_undo +ruby/dyn +tag_old_static +toolbar +wildignore -xterm_clipboard +balloon_eval +cmdline_hist +diff +file_in_path +iconv +lispindent +mouse_dec +multi_lang +postscript +scrollbind -tag_any_white +transparency +wildmenu -xterm_save +browse +cmdline_info +digraphs +find_in_path +insert_expand +listcmds -mouse_gpm -mzscheme +printer +signs -tcl +user_commands +windows ++builtin_terms +comments +dnd +float +job +localmap -mouse_jsbterm +netbeans_intg +profile +smartindent +termguicolors +vertsplit +writebackup +byte_offset +conceal -ebcdic +folding +jumplist +lua/dyn +mouse_netterm +num64 +python/dyn +startuptime +terminfo +virtualedit -X11 +channel +cryptv +emacs_tags -footer +keymap +menu +mouse_sgr +odbeditor +python3/dyn +statusline +termresponse +visual -xfontset +cindent +cscope +eval +fork() +lambda +mksession -mouse_sysmouse +packages +quickfix -sun_workshop +textobjects +visualextra +xim system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "$VIM/gvimrc" user gvimrc file: "$HOME/.gvimrc" 2nd user gvimrc file: "~/.vim/gvimrc" defaults file: "$VIMRUNTIME/defaults.vim" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim" Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe -DMACOS_X_UNIX -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: clang -L. -fstack-protector -L/usr/local/opt/libyaml/lib -L/usr/local/opt/readline/lib -L/usr/local/opt/libksba/lib -L/usr/local/opt/openssl/lib -L. -fstack-protector -L/usr/local/opt/libyaml/lib -L/usr/local/opt/readline/lib -L/usr/local/opt/libksba/lib - L/usr/local/opt/openssl/lib -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon -lm -lncurses -liconv -framework Cocoa -fstack-protector -L/System/Library/Perl/5.16/darwin-thread-multi-2level/CORE Press ENTER or type command to continue