Alfred stuck as process parent in Ventura, breaks monitoring & control

[ideologysec]

I use several applications for monitoring my system, including iStat Menus and Little Snitch.

Recently with Ventura, Alfred is now the parent process of Google Chrome, which means that it is the process showing up as utilizing all of Chrome's memory, attempting to make network connections, etc. This breaks per-application network control (I don't really want Alfred having unrestricted internet access), and useful monitoring (memory, CPU usage, etc).

This only happens if alfred-chrome is used to launch Chrome for the first time. If Chrome is already running, using alfred-chrome to launch different profiles or switch to Chrome doesn't result in this behavior.

This is a minor issue, but it's helpful for me to be able to launch Chrome with a specific profile, and this breaks that workflow a bit.

System Specs:
Hardware: 14" MacBook Pro M1 Max, 64 GB RAM
Software: macOS 13.1 Ventura, running in Reduced Security Mode (User approved kernel extensions allowed)
alfred-chrome version: 5.0.0

Happened both with previous versions, and the new v5 Rust rewrite.

[ShogunPanda]

Hello!
I just released 5.1.0 which should use setsid to detach the process. Can you please tell me if it works?

[ideologysec]

Still seemingly inheriting Alfred as the parent process:

[ShogunPanda]

Yes, from monitoring activity it still shows like that, but from my test it should be no longer the case. For instance in the previous version (5.0.0) quitting Alfred would have quit Chrome as well. In 5.1.0 it will not.
Other than that, do you still have the monitor problem above. In other words, if you prevent Alfred to talk to the network, will Chrome work?

[ideologysec]

If I block access to "Alfred" after launching , then Chrome won't work, no.

[ShogunPanda]

Ok, I see, thanks. I will review this ASAP to find alternative ways to launch Chrome outside of Alfred.