Some terminals may raise the SIGWINCH(28) signal when the TTY window is resized amidst an interactive job session when the job is running.
This would lead to the SIGWINCH signal being trapped by the signal handler and the job being halted abruptly causing a SIGPIPE.
This can happen anywhere in the job session, although affects mainly jobs being run over an IP link.
We have fixed this in version 220.127.116.11 so that you can resize the terminal window freely while the job is running. The SIGWINCH signal is just ignored now.