I just done a fresh installation of Vim, and with this occasion I added some new plugins to my VIM configuration. The problem is that now, when I do the first change in the file, VIM blocks and one of my CPUs reach 100% load. This is also happening every now and then while I'm editing the file. This never happened in the previous configuration. How can I find what plugin is killing my CPU?
As an alternative to romainl's (nice and simple) trial-and-error approach:
I've done such once using vim's built-in profiler: :he profile
.
You might need to compile vim by yourself to activate (profiling is not enabled in the default vim distribution).
Then
:profile start filename
to activate profiling and write your profile data to filename
, edit your file (which pushes the CPU to 100%), once done
:profdel
to stop profiling. Quit vim and you'll find the profiling information written in filename
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With