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
{{ message }}
This repository has been archived by the owner on Apr 1, 2020. It is now read-only.
Oni Version: 0.3.9 Operating System: macOS 10.14.6
Issue: As soon as I initiate the colon-command GUI, the oni process spikes over 100% and stays there no matter how long I have the menu open (even without typing). For context, this CPU spike doesn't happen when I open up similar GUIs like the fuzzy finder or command palette.
I've also confirmed that it isn't due to a leaky vim config, as nvim inside terminal doesn't spike the CPU at all. It severely impacts the UX for me, since typing colon commands becomes incredibly laggy. Especially when trying to tab out a file path. It's so delayed that I have to anticipate the lag a few seconds ahead of typing.
Expected behavior: There should be zero reason for the CPU to spike when issuing colon-commands. Especially when I'm not actively trying to get autocomplete suggestions. I'm simply typing letters into a text box.
Actual behavior: CPU spikes to over 100% usage as soon as I hit the colon key.
Steps to reproduce: Open oni normal mode, press the : key.
The text was updated successfully, but these errors were encountered:
Hello and welcome to the Oni repository! Thanks for opening your first issue here. To help us out, please make sure to include as much detail as possible - including screenshots and logs, if possible.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Oni Version: 0.3.9
Operating System: macOS 10.14.6
Issue: As soon as I initiate the colon-command GUI, the oni process spikes over 100% and stays there no matter how long I have the menu open (even without typing). For context, this CPU spike doesn't happen when I open up similar GUIs like the fuzzy finder or command palette.
I've also confirmed that it isn't due to a leaky vim config, as nvim inside terminal doesn't spike the CPU at all. It severely impacts the UX for me, since typing colon commands becomes incredibly laggy. Especially when trying to tab out a file path. It's so delayed that I have to anticipate the lag a few seconds ahead of typing.
Expected behavior: There should be zero reason for the CPU to spike when issuing colon-commands. Especially when I'm not actively trying to get autocomplete suggestions. I'm simply typing letters into a text box.
Actual behavior: CPU spikes to over 100% usage as soon as I hit the colon key.
Steps to reproduce: Open oni normal mode, press the
:
key.The text was updated successfully, but these errors were encountered: