> Could you please test if additional SIGCHLD can release hanging? Start mintty and check the process from another bash.
$ ps PID PPID PGID WINPID TTY UID STIME COMMAND 1713 1662 1713 6800 cons0 197609 04:26:01 /usr/bin/ps 1671 1 1671 6072 ? 197609 04:25:47 /usr/bin/mintty I 1672 1671 1672 2096 pty0 197609 04:25:48 /usr/bin/zsh 1662 1 1662 4696 cons0 197609 04:24:21 /usr/bin/bash After typing enter into zsh several times, the prompt is not returned. $ ps PID PPID PGID WINPID TTY UID STIME COMMAND 1728 1727 1672 3948 pty0 197609 04:26:10 /usr/bin/zsh 1731 1662 1731 7644 cons0 197609 04:26:14 /usr/bin/ps 1727 1672 1672 4076 pty0 197609 04:26:10 /usr/bin/zsh 1671 1 1671 6072 ? 197609 04:25:47 /usr/bin/mintty 1672 1671 1672 2096 pty0 197609 04:25:48 /usr/bin/zsh 1662 1 1662 4696 cons0 197609 04:24:21 /usr/bin/bash SIGCHLD is sent to zsh with mintty as parent, but nothing seems to change. $ kill -CHLD 1672 $ ps PID PPID PGID WINPID TTY UID STIME COMMAND 1728 1727 1672 3948 pty0 197609 04:26:10 /usr/bin/zsh 1727 1672 1672 4076 pty0 197609 04:26:10 /usr/bin/zsh 1671 1 1671 6072 ? 197609 04:25:47 /usr/bin/mintty 1672 1671 1672 2096 pty0 197609 04:25:48 /usr/bin/zsh 1733 1662 1733 5388 cons0 197609 04:33:39 /usr/bin/ps 1662 1 1662 4696 cons0 197609 04:24:21 /usr/bin/bash If SIGKILL is accepted, zsh will exit with mintty, but zsh's descendant processes will remain. > Are any additional settings necessary? - zsh is specified by the environment variable SHELL. - HOME is a symbolic link. (`/home/myname` -> `/cygdrive/c/Users/myname`) - My cygwin environment is arm64 (M1 MacBook Pro). Windows is installed on UTM. ( https://mac.getutm.app/ ) - Since I have several packages that I built myself, they may be causing the problem. On Sat, Dec 21, 2024 at 7:47 PM Takashi Yano via Cygwin <cygwin@cygwin.com> wrote: > > On Sat, 21 Dec 2024 19:40:59 +0900 > Takashi Yano wrote: > > On Sat, 21 Dec 2024 12:30:02 +0900 > > Daisuke Fujimura wrote: > > > Sometimes the prompt does not return. > > > > > > $ ps > > > PID PPID PGID WINPID TTY UID STIME COMMAND > > > 378 294 378 5544 pty0 197609 11:26:16 /usr/bin/ps > > > 351 1 294 6552 pty0 197609 10:13:07 /usr/bin/zsh > > > 293 1 293 4984 ? 197609 10:13:03 /usr/bin/mintty > > > 294 293 294 2840 pty0 197609 10:13:04 /usr/bin/zsh > > > $ > > > # Pressing enter only without typing anything may not return a prompt. > > > (Send SIGINT by Ctrl-C) > > > $ ps > > > PID PPID PGID WINPID TTY UID STIME COMMAND > > > 351 1 294 6552 pty0 197609 10:13:07 /usr/bin/zsh > > > 407 294 407 1976 pty0 197609 11:26:24 /usr/bin/ps > > > 293 1 293 4984 ? 197609 10:13:03 /usr/bin/mintty > > > 404 1 294 9660 pty0 197609 11:26:19 /usr/bin/zsh > > > 294 293 294 2840 pty0 197609 10:13:04 /usr/bin/zsh > > > > > > > > > $ zsh --version > > > zsh 5.8 (x86_64-pc-cygwin) > > > > > > $ uname -srvmpio > > > CYGWIN_NT-10.0-22000 3.5.5-1.x86_64 2024-12-20 16:19 UTC x86_64 > > > unknown unknown Cygwin > > > > > > $ cd /path/to/oh-my-zsh > > > $ git log --oneline -1 > > > b9e73b4 (HEAD -> master, origin/master) docs(per-directory-history): > > > add variable docs (#12844) > > > > > > Removing `source /path/to/oh-my-zsh/oh-my-zsh.sh` from `~/.zshrc` will > > > not cause such problems. > > > > > > Cygwin-3.5.4-1 does not have this problem. > > > > Could you please test if additional SIGCHLD can release hanging? > > kill -SIGCHLD <pid_of_hanging_zsh> > > Oops! > s/SIGCHLD/CHLD/ > > -- > Takashi Yano <takashi.y...@nifty.ne.jp> > > -- > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation: https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
