Find process got stuck in the background and led to high CPU usage

[duhd1993]

• [x] I have read through the manual page (man fzf)
• [x] I have the latest version of fzf
• [x] I have searched through the existing issues

Info

• OS
  • [ ] Linux
  • [x] Mac OS X
  • [ ] Windows
  • [ ] Etc.
• Shell
  • [ ] bash
  • [ ] zsh
  • [x] fish

Problem / Steps to reproduce

After using fzf in shell, a process of find is left behind and consumes a whole core of cpu This seems to be a process run by fzf. Once it gets hung there, even kill -9 does not work on it. I can only restart my whole machine. After restarting, I cannot reproduce this problem. But it might happen again unless I figure out what's the problem. Appreciate if you could provide some clues.

Another question, in the shell, I use Ctrl-T to call fzf. When this bug happens, it won't go back to shell prompt after ESC. fzf does quit but I have to Ctrl-C to get back to shell. Not sure if this is related but feels suspicious.

[junegunn]

I'm not sure what's going on there. But I guess you'll have better luck if you build fzf from the latest source which includes #2382.

[duhd1993]

Thank you. I will give it a try, though it's different in my case where find instead of fzf does not quit properly.

[nyngwang]

So, does anyone still care about this issue now? I am a NeoVim user and I experience high CPU usage too when scrolling on the searching result list.