You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably related to: #7871, though that was primarily about a memory leak.
Actual behavior
Without vim-airline, neovim consumes 1%--2% CPU. Pressing space to stop the timer makes the CPU go to 0%.
With vim-airline, neovim consumes 10%--12% CPU. Again, pressing space makes the CPU go to 0%.
To emphasize, I am not claiming this is any bug in vim-airline, but the presence of vim-airline exacerbates the issue many-fold, which may help in determining the cause.
Expected behaviour
There should be no CPU activity when timers are paused. In vim, there is apparently no cost to having timers paused.
The text was updated successfully, but these errors were encountered:
nvim --version
: NVIM v0.2.2$TERM
: xterm-256colorSteps to reproduce:
Here is an example init.vim:
run:
and
htop
or similar.This is probably related to: #7871, though that was primarily about a memory leak.
Actual behavior
Without vim-airline, neovim consumes 1%--2% CPU. Pressing space to stop the timer makes the CPU go to 0%.
With vim-airline, neovim consumes 10%--12% CPU. Again, pressing space makes the CPU go to 0%.
To emphasize, I am not claiming this is any bug in vim-airline, but the presence of vim-airline exacerbates the issue many-fold, which may help in determining the cause.
Expected behaviour
There should be no CPU activity when timers are paused. In vim, there is apparently no cost to having timers paused.
The text was updated successfully, but these errors were encountered: