[SOLVED] Killing fish reparents some ncurses processes into CPU hogs

I've had issue when killing a fish shell running an ncurses app (fzf, ncdu, cmus, ranger...): it will randomly (about 75% of the time, ymmv) reparent the ncurses process to PID1 and turn it into a CPU hog.

I cannot reproduce with either xterm+fish or URxvt+bash.I hadn't thought of TTY, so I tried anyways: rightfully so, TTY+fish will create a CPU hog!So Awesome has nothing to do with it.Still weird that I cannot reproduce with xterm.

It sounds like fish is failing to send and/or propogate signals (SIGTERM/SIGKILL) to child process resulting in broken pipes for any children that require standard stream connections (all the ones you mention do).

Ideally, the child programs should detect the broken pipe and exit gracefully. So really it is a bug on their end too. But it seems the de facto standard is for many of these programs to rely on the shell or other parent program to let them know then the terminal is gone.