lockfile descriptor persist through signal system

[asmvik]

I noticed that sometimes this happens:

If I do the yabai --stop-service one is gone but the other remains
Even killing the process with pkill yabai doesn't do anything.
One process is listed forever.
I guess this is the reason both processes fight for lock.

I also noticed that often times when I was connecting/disconnecting external monitor I saw additional yabai process (without icon) that disappeared after about 5 seconds

I rebooted my machine and in my script for display_changed event

yabai -m signal --add event=display_changed action="$HOME/.local/switch-flow/scripts/handle_display_changed.sh" &

note: this screenshot is taken after reboot so don't mind the PID being different from the other screenshot.

I added sleep 5 before yabai -m query --windows id,app,title
Now when I connect/disconnect the external monitor the "additional" yabai process doesn't show up.
Maybe this will give you some hints.
Perhaps too much was happening after display_changed event in my setup and that overwhelmed yabai.
It's quite possible that I haven't noticed this before because I started to use external monitor few weeks ago and that enforced some changes in my setup.

Originally posted by @kmiterror in #2770

[kmiterror]

This is a follow-up to my previous message (the one from #2770 issue )
Perhaps this will shed some light on the actual issue.

I just noticed that one of the yabai processes is started through launchd and the other is not.
When I checked with launchctl list | grep -i yabai I got this com.koekeishiya.yabai
But I when I do this yabai --stop-service I get this Could not find service "com.asmvik.yabai" in domain for user gui: 501
So I guess that the name change of your github handle affected how this operate in real life.
You can actually start 2 competing services that share the same lock file "yabai_[username].lock"
I was using yabai long before the name was changed.
Does this make sense now?

To fix the issue on my machine I did this:

1. Stop and unload the old service

launchctl unload ~/Library/LaunchAgents/com.koekeishiya.yabai.plist 2>/dev/null || \
launchctl unload /Library/LaunchAgents/com.koekeishiya.yabai.plist 2>/dev/null || \
launchctl bootout gui/$(id - u) com.koekeishiya.yabai 2>/dev/null

2. Kill any running yabai processes

pkill yabai

3. Remove the old plist if it exists

rm -f ~/Library/LaunchAgents/com.koekeishiya.yabai.plist
rm -f /Library/LaunchAgents/com.koekeishiya.yabai.plist

4. Now use the new yabai CLI to install and start the service

yabai --start-service

And now after launchctl list | grep -i yabai
I get this:
23092 0 com.asmvik.yabai
and all yabai --stop-service/yabai --start-service commands are working properly.