Slowdown / lockups reading helpfiles

[steen]

I'm having a rather odd issue and am having no luck googling.

Whenever I try to load a helpfile, the response time is _extremely_
slow, sometimes to the point of locking my window for upwards of 10
seconds. Also, CPU gets pegged by the Vim process. True of macvim and
console vim, it feels like macvim is getting harder hit, but that's a
very subjective perception. This only seems to happen loading
helpfiles, everything else I do in vim seems to be working just fine.
I am working under the assumption that this is due to some plugin that
I have recently installed, and so I'm going to probably just deal with
this by stepping through disabling them until stuff works again. But
it strikes me as odd that any plugin could do anything to just affect
the reading of helpfiles.

So, any pointers or tips for narrowing down the culprits here?

[Mac OS 10.7.3, vim 7.3]

Thanks in advance,
-- Steen

--
You received this message from the "vim_use" 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

[MarcWeber]

Excerpts from steen's message of Thu Jun 21 12:47:19 +0200 2012:
> this by stepping through disabling them until stuff works again. But
> it strikes me as odd that any plugin could do anything to just affect
> the reading of helpfiles.
Yes - that's the way to go.

Start by moving your .vimrc and your .vim out of the way - then you know
whether' its vim fault (that would have taken less time than writing
your mail).

If its caused by your .vimrc and or .vim/ then disabling plugins
piecewise will help. vim-addon-manager may be very helpful for such
testing. switiching filetype plugin etc off may also give some pointners
where to start.

But why am I telling you this? It looks you already know it ..

Also vim -V20/tmp/log will write a logfile.
If you watch it before opening a help file and afterwards you see which
VimL lines got executed.

Marc Weber

--
You received this message from the "vim_use" 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

[steen]

On Thu, Jun 21, 2012 at 3:57 AM, Marc Weber <[hidden email]> wrote:
>
> If its caused by your .vimrc and or .vim/ then disabling plugins
> piecewise will help. vim-addon-manager may be very helpful for such
> testing. switiching filetype plugin etc off may also give some pointners
> where to start.
>
> But why am I telling you this? It looks you already know it ..

vim-addon-manager I hadn't looked into, actually. That may be extremely helpful.

>
> Also vim -V20/tmp/log will write a logfile.
> If you watch it before opening a help file and afterwards you see which
> VimL lines got executed.

That, otoh, I had no idea of, and will definitely be helpful. Thanks!

--Steen
>
> Marc Weber
>
> --
> You received this message from the "vim_use" 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 from the "vim_use" 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