iTerm2 wrongly thinks processes are still running; this blocks Cmd-W
Thanks for filing an issue! Please answer the questions below so I can help you.
- iTerm2 version: 3.3.0beta8
- OS version: 10.14.5
Detailed steps to reproduce the problem:
- Open a fresh iTerm2 window.
- Launch a program that "lasts" a while (e.g., vim or mutt).
- Quit that program and then as soon as you see your shell prompt return, hit Cmd-W.
What happened: I get a dialog box asking if I'm sure I want to close the tab, because "this tab is running vim".
What should have happened: The iTerm2 window should've just closed without any prompt. That's how it's always worked (I just tested it in 3.2.9). More importantly, vim was already quit, and I was back at the shell prompt. So iTerm2 should already "know" that vim is no longer running.
I just started noticing this within the last few weeks, but it might have begun earlier in the beta sequence. I can't exactly set a stopwatch for this, but it seems like after I quit a program and get the shell prompt back, there's maybe a half-second window where iTerm2 wrongly believes that program is still running and throws a dialog box.
Is this new behavior on purpose? If so, is there some new preference that I didn't notice that would eliminate this?