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

macOS Errors Intermediate 👁 14 views 📅 May 25, 2026

The com.apple.launchd.peruser error indicates a per-user launchd process crash loop. This guide covers symptoms, causes, and step-by-step fixes to stop the repeated crashes.

Symptoms

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

  • Repeated pop-up or console messages stating that com.apple.launchd.peruser has crashed and is being restarted.
  • System sluggishness or unresponsiveness as the launchd process repeatedly restarts.
  • High CPU usage caused by the crash loop.
  • Applications may fail to launch or behave erratically.
  • System logs (/var/log/system.log or Console app) show entries like com.apple.launchd.peruser[PID]: (path) Exited with code: 1 followed by com.apple.launchd.peruser[PID]: (path) Throttling respawn: Will start in X seconds.

Root Causes

The com.apple.launchd.peruser process manages per-user launch agents and daemons. A crash loop typically occurs due to one of the following:

  1. Corrupted or misconfigured user launch agent plist files – A plist in ~/Library/LaunchAgents or /Library/LaunchAgents may have syntax errors or reference missing executables.
  2. Third-party software conflicts – Applications that install user-level launch agents (e.g., Adobe, Dropbox, antivirus) can cause instability.
  3. Damaged user preferences or caches – Corrupted preference files (.plist) can interfere with launchd.
  4. System file corruption – Rarely, macOS system files related to launchd may be damaged.
  5. Insufficient permissions – Incorrect ownership or permissions on user launch agent files.

Step-by-Step Fix

Step 1: Identify the Problematic Launch Agent

  1. Open Console app (from /Applications/Utilities).
  2. In the search bar, type com.apple.launchd.peruser.
  3. Look for entries showing Exited with code and note the path of the agent (e.g., /Users/username/Library/LaunchAgents/com.example.agent.plist).
  4. Alternatively, run this command in Terminal:
    sudo launchctl list | grep -v "com.apple"
    to see non-Apple user agents. Look for agents with a non-zero exit status.

Step 2: Disable or Remove the Offending Agent

  1. Once you have the agent path, unload it:
    launchctl unload ~/Library/LaunchAgents/com.example.agent.plist
  2. If the crash stops, the agent is the cause. Move it to a backup location:
    mv ~/Library/LaunchAgents/com.example.agent.plist ~/Desktop/
  3. If the agent is in /Library/LaunchAgents or /System/Library/LaunchAgents, you may need sudo and caution. For system agents, consider reinstalling the associated software.

Step 3: Clear User Cache and Preferences

  1. In Terminal, run:
    rm -rf ~/Library/Caches/*
  2. Remove problematic preference files (backup first):
    cd ~/Library/Preferences
    ls -la | grep plist
    Look for files related to the crashing agent (e.g., com.example.agent.plist) and delete them:
    rm com.example.agent.plist

Step 4: Repair Permissions

  1. Run:
    sudo chown -R $(whoami) ~/Library/LaunchAgents
  2. Repair disk permissions (macOS High Sierra and earlier):
    sudo diskutil repairPermissions /
    For macOS Mojave and later, use First Aid in Disk Utility.

Step 5: Reboot and Monitor

  1. Restart your Mac:
    sudo shutdown -r now
  2. After reboot, check Console for any recurrence of the error.

Alternative Fixes

  • Create a new user account – If the issue is user-specific, log in to a new account. If the error disappears, migrate your data to the new account.
  • Reset NVRAM/PRAM – Restart and hold Option+Command+P+R for 20 seconds.
  • Reinstall macOS – Use Recovery Mode to reinstall macOS without erasing data (preserves user files).
  • Use Safe Mode – Boot into Safe Mode (hold Shift during startup) to disable third-party launch agents. If the crash stops, a third-party agent is likely the cause.

Prevention

  • Regularly update macOS and third-party software to avoid compatibility issues.
  • Before installing new software, check if it adds launch agents and review their plist files.
  • Back up your Mac with Time Machine to restore corrupted files if needed.
  • Avoid manually editing plist files unless you are certain of the syntax.
  • Periodically review ~/Library/LaunchAgents and remove unused agents.

By following these steps, you can resolve the com.apple.launchd.peruser crash loop and restore normal system operation.

Was this solution helpful?