-
-
Couldn't load subscription status.
- Fork 225
Closed as not planned
Labels
bugSomething isn't workingSomething isn't working
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
When using bufferline.nvim and compiling tex (particularly large ones) in the background, neovim becomes unresponsive, and its CPU usage spikes to 100%. This issue resolves once the compilation process is complete. I profiled with snacks.profiler, and this function is identified to be the most time-consuming one (it's invoked with an unusually high frequency)
| local buf_nums = utils.get_valid_buffers() |
The maintainer of vimtex has no clue and suspects it's bufferline.nvim's issue.
What did you expect to happen?
normal cpu usage when vimtex is compiling
Config
Additional Information
...
commit
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working