macOS: login processes not reaped from closed surfaces
#2273
Labels
Comments
|
This appears to only affect macOS. I've got a fix working... needs more testing stand by. |
mitchellh
added a commit
that referenced
this issue
Sep 20, 2024
Fixes #2273 On macOS, killpg is expected to fail with EPERM because of the way we launch a login process around it. Before this commit, this caused us to never call waitpid and reap the child process, which caused the child process to stick around as a zombie. This commit allows killpg to fail with EPERM on macOS and fall through to waitpid.
|
I appear to be seeing this issue. Not sure if there has been a regression with this fix or something else. My environment is macOS Sequoia 15.2, I have build my own Capturing some logging, I don't see much, when I exit a shell, not sure what I should expect though |
|
I'm also seeing a lot of defunct processes. |
|
I have started a discussion since this current defunct process list seems different - #3596 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Full disclosure: I don't know as much about Unix process life cycles as I ought to, but:
When a surface is closed, the processes inside are properly killed and reaped and gone, but the
loginprocess (owned byroot? no clue if that's relevant) remains as a sleeping "<defunct>" process. This isn't a really terrible bug, but definitely isn't correct and should probably be tracked down and fixed.The text was updated successfully, but these errors were encountered: