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
Its not always, but I noticed that when you try doing a search that will result in a lot of entries, it first displays a weird error (its gigantic, so I will paste it below), and then it starts the async search, and whenever I switch to the search buffer, my normal buffer gets replaced with the same contents as the search buffer (minus highlighting, image showing this below), and whenever I try to close any of the buffers (by doing :bd or :q), neovim crashes and the following message appears on the console:
Theres nothing in specific on any file, its random, I can make the same search twice, and first it breaks, and then it works fine... I noticed it usually happen on async searches, with lots of results being displayed
The text was updated successfully, but these errors were encountered:
The error messages implies it's more likely a problem related to nvim. Sorry for that I'm not using nvim so I can't figure out the root cause, but updating your nvim to latest or downgrading to a specific stable version may help.
Issue description
Its not always, but I noticed that when you try doing a search that will result in a lot of entries, it first displays a weird error (its gigantic, so I will paste it below), and then it starts the async search, and whenever I switch to the search buffer, my normal buffer gets replaced with the same contents as the search buffer (minus highlighting, image showing this below), and whenever I try to close any of the buffers (by doing
:bd
or:q
), neovim crashes and the following message appears on the console:the neovim crash
free(): invalid pointer zsh: abort (core dumped) nvim %
the buffer being replaced with a copy of the search buffer (it updates whenever the search buffer updates as well):
the gigantic first error:
Things about your system and environment
Its difficult to post the log, as there's a lot of private code as well in there... If there's anything in specific, I can try to search for it
Theres nothing in specific on any file, its random, I can make the same search twice, and first it breaks, and then it works fine... I noticed it usually happen on async searches, with lots of results being displayed
The text was updated successfully, but these errors were encountered: