2009/7/23 Zvezdan Petkovic:
>
> MacVim snapshot 47 consistently froze for me today with a very simple
> search (about 10 times in a row with restarts and reinstalling of Vim).
>
> :vimgrep remove_invisible_markup src/project/src/package/**/*
>
> MacVim never came back from that search and consumed 100% of the CPU.
> I had to use "kill -9 PID" from the terminal or Force Quit from
> Activity Monitor to stop it.
Was the "MacVim" process consuming 100% CPU or was it a "Vim" process?
If the latter, does it work to press Cmd-. to interrupt the process?
> I run these kinds of searches all the time and never had an issue
> before. I tried the search above with /remove_invisible_markup/ too
> with the same result.
>
> The search before the above one, for a word "summary", worked just fine.
>
> Since I had other work to finish, I couldn't trace down the problem
> cause. Instead, I downgraded to Snapshot 45 which works fine for me.
>
> Perhaps someone will have an idea what changed between the snapshots
> that could cause this behaviour.
I can't really guess what's going on without more information. Is
there a simple and reliable way to reproduce the bug?
It would help if you sent me the logs from when it crashed. Do this:
1. Open Terminal and enter
$ defaults write org.vim.MacVim MMLogLevel 7
$ defaults write org.vim.MacVim MMLogToStdErr 1
2. Quit MacVim and start it from Terminal with "mvim" (lots of debug
info will be logged to Terminal, it may help if you redirect stderr to
a file when you start "mvim")
3. Reproduce the crash, copy&paste log info and email it to me directly
4. Reset logging levels
$ defaults delete org.vim.MacVim MMLogLevel
$ defaults delete org.vim.MacVim MMLogToStdErr
Thanks,
Björn
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
