Disabling photoanalysisd

disabling-photoanalysisd.md

For what it's worth (and with all the usual disclaimers about potentially making your mac unstable by disabling system services), here's some commands that will manipulate this service and services like it. Note the $UID in the command, that's just a bash shell variable that will resolve to some number. That's your numeric UID. You just run these commands from a Terminal command line. No special privileges needed.

If you want to disable it entirely, the first command stops it from respawning, and the second kills the one that is currently running:

launchctl disable gui/$UID/com.apple.photoanalysisd
launchctl kill -TERM gui/$UID/com.apple.photoanalysisd

(If you kill it without disabling it will die, but a new one will respawn and pick up where the old one left off)

I don't have this problem myself, so I can't try these next two commands. They're relying on good ole UNIX signals. You could theoretically suspend and resume the process like this ("STOP" and "CONT" are stop and continue):

launchctl kill -STOP gui/$UID/com.apple.photoanalysisd
launchctl kill -CONT gui/$UID/com.apple.photoanalysisd

I don't know what launchd does when running processes are suspended for a long time. Will it detect them as dead and kill and restart them? I dunno. But I do know they won't get any CPU time.

https://www.reddit.com/r/MacOS/comments/5887s9/photoanalysisd_macos_sierras_most_contentious_new/

Sadly, this doesn't seem to work now. I've pretty much tried everything... killing it is not an issue, but I can't find the configuration respawning it. Furthermore, I have no photos in this laptop (work), Photos shows 0, so I guess I'm processing someone else photos?
I'd love to see what's happening, but I can'tteven get to the library directory, where I suppose the DB is held:
ls '/Users/me/Pictures/Photos Library.photoslibrary' ls: Photos Library.photoslibrary: Operation not permitted

Mine didnt go away till I closed preview. Seems like that might count now

This piece of image recognition spyware, introduce by Apple, is harder than ever to get rid of in OS Catalina. The instructions for previous versions of MacOS worked. Apple apparently reads our solutions to this nightmare of a problem then figures out new ways to prevent us from stopping it. So, here's what I am doing and it appears it may work. I'm moving the .plist file to the LaunchAgentsIgnored directory OR just moving it to a whole different part of the filesystem.

I'm moving the relevant files to a folder in my Documents directory called Evilstuff.

You must have ROOT user enabled on your system for this to work.

Deactivate System Integrity Protection

1) Turn off the Mac
2) Hold down Command-R for about ten seconds and press power button
3) Wait for OS X to boot into the OS X Utilities Window
4) Choose Utilities -> Terminal
5) # csrutil disable
6) # reboot

Remove or rename the photoanalysisd file

# su
# mount -uw /
# mv -v /System/Library/LaunchAgents/com.apple.photoanalysisd.plist /Users/[myusername]/Documents/Evilstuff
# mv -v /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Versions/A/Support/photoanalysisd /Users/[myusername]/Documents/Evilstuff

Reactivate System Integrity Protection

1) Turn off the Mac
2) Hold down Command-R for about ten seconds and press power button
3) Wait for OS X to boot into the OS X Utilities Window
4) Choose Utilities -> Terminal
5) # csrutil enable
6) # reboot

I am going to watch and see if it comes back. It is sure to do so, with the next update/patch from Apple, so I'm keeping these instructions handy.

I'm testing another solution that I found on StackExchange

1. start Photos, let it continue past the first dialogue box;
2. now Preferences in the app menu is clickable (it wasn't before);
3. Preferences > General , and untick both check boxes in Memories;
4. close Photos.
   This stops photoanalysisd cold, no reboot or kill required.

---

Upd: The process became less voracious, but still it consumes cpu time

I'm testing a composite of solutions, since none of the above are idea. I noticed that there's a delay element available in the plist. Until I have a chance to reboot the machine into Systems Integrity Protection off, I'm doing this:

su
while true do
    killall photoanalysisd
    sleep 10
done

which keeps the beast quiet until I figure it out.

And the delay does nothing, as that's for launchd and it doesn't use launchd for its looping behaviour. SIGH.

The permanent fix:
https://apple.stackexchange.com/questions/338001/how-to-prevent-the-photos-app-from-launching-cloudphotosd-photoanalysisd-etc/413685#413685

The solution from @ElectronHerder worked for me eventually.
Many thanks for giving me back the peace of a calm and not-glowing macbook.

Except for the "su" command. This command always yielded "Sorry". Then I read somewhere that the root user was protected on Mac OS X.
Use "sudo su -" instead, if you have the same issue.

You can get your $UID by running id.
$UID was not a set environment variable for me in my terminal.

I have 0 (ZERO) photos in my library. I don't use photos or even iCloud Drive for photos storage in any way. Even after reinstall Catalina the problema persists. This thread are kept in my favorites forever.

So many thanks to @huksley , the sub reddit and stackexchange.

Small change needed for Monterey. The command to disable the service is now

launchctl disable user/$UID/com.apple.photoanalysisd

The gui changed to user. The command to kill the process is the same

launchctl kill TERM gui/$UID/com.apple.photoanalysisd

I don’t know about the “tracked” part but “ somebody “ left a mighty big (nearly 16 MB) footprint!!!

Powerstats for: photoanalysisd [1389]
UUID:
EE+**++-346A-388F-@@++
Path:
/System/Library/PrivateFrameworks/PhotoAnalysis.framework/Support/photoanalysisd
Resource Coalition ID: 4((
Architecture:
arm64e
Parent:
UNKNOWN [11
UID:
5&1
Sudden Term:
Tracked (allows idle exit)
Footprint:
12.16 MB -> 15.70 MB (+3632 KB)
Pageins:
273 pages
Start time:
2023-05-12 01:34:49.369 -0500
End time:
2023-05-12 01:37:01.563 -0500
Num samples:
39 (89%)
Primary state: 34 samples Non-Frontmost App, Non-Suppressed, User mode, Effective Thread QoS Background, Requested
Thread QoS Background, Override Thread QoS Unspecified
User Activity: 39 samples Idle, O samples Active
Power Source:
O samples on Battery, 39 samples on AC