Fix com.apple.launchd.peruser Error Crash Loop on macOS

The com.apple.launchd.peruser error crash loop occurs when user-level launchd processes repeatedly crash, often due to corrupted plist files or permission issues. This guide provides step-by-step fixes to resolve the loop and restore system stability.

Symptoms

Users experiencing the com.apple.launchd.peruser error crash loop may notice the following symptoms:

Repeated pop-up error messages indicating that a user-level launchd process has crashed and is being restarted.
System performance degradation, including sluggishness and high CPU usage.
Applications failing to launch or crashing unexpectedly.
Console logs filled with entries like com.apple.launchd.peruser.501 (where 501 is the user ID) crashing repeatedly.
Inability to log out or shut down properly.

Root Causes

The crash loop is typically caused by one of the following:

Corrupted user LaunchAgents plist files: A misconfigured or damaged property list file in ~/Library/LaunchAgents can cause launchd to crash repeatedly.
Incorrect file permissions: launchd requires strict permissions (usually 644 for plist files). Incorrect permissions can trigger crashes.
Third-party software conflicts: Some applications install unstable launchd agents that may cause crashes.
System file corruption: Rarely, system-level launchd configuration files may become corrupted.
User account corruption: A damaged user account can lead to launchd instability.

Step-by-Step Fix

Step 1: Identify the Crashing Process

Open Console app from /Applications/Utilities.
In the search bar, type launchd or peruser.
Look for crash logs that include the user ID (e.g., com.apple.launchd.peruser.501). Note the exact plist file name mentioned in the error.

Step 2: Disable or Remove Problematic LaunchAgents

Open Terminal from /Applications/Utilities.
Navigate to the user LaunchAgents folder:
```
cd ~/Library/LaunchAgents
```
List all plist files:
```
ls -la
```
Identify the problematic plist from the Console logs. For example, if the log mentions com.example.broken.plist, move it to a backup location:
```
mkdir ~/Desktop/launchd_backup
mv com.example.broken.plist ~/Desktop/launchd_backup/
```

Unload the agent (if still running):

launchctl unload ~/Library/LaunchAgents/com.example.broken.plist

Restart your Mac to clear the crash loop.

Step 3: Repair Permissions

In Terminal, fix permissions on all LaunchAgents:

chmod 644 ~/Library/LaunchAgents/*.plist
chown $USER:staff ~/Library/LaunchAgents/*.plist

If you suspect system-level issues, repair system permissions (macOS Catalina and earlier):
```
sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /
```
For macOS Big Sur and later, use First Aid in Disk Utility to repair the disk.

Step 4: Check for Third-Party Conflicts

Boot into Safe Mode (hold Shift at startup) to temporarily disable all third-party LaunchAgents.
If the crash stops, the issue is likely caused by a third-party agent. Use the steps above to identify and remove it.

Step 5: Create a New User Account

Go to System Preferences > Users & Groups.
Click the lock to make changes, then click + to create a new user.
Log out of the current account and log into the new one.
If the crash loop is gone, the original user account is corrupted. Migrate data using Migration Assistant.

Alternative Fixes

Reset NVRAM/PRAM: Restart and hold Option + Command + P + R for 20 seconds to reset parameter RAM.
Reinstall macOS: If all else fails, reinstall macOS via Recovery Mode without erasing your data.
Use OnyX: Download OnyX (free utility) to clean system caches and repair permissions.

Prevention

Regularly update macOS to the latest version to benefit from bug fixes.
Avoid installing untrusted software that may include unstable launchd agents.
Back up your Mac regularly with Time Machine to recover from corruption.
Monitor Console logs periodically to catch launchd issues early.
Keep LaunchAgents folder clean by removing unused plist files.