What is launchd_sim, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path inside the iOS 26.5 and watchOS 26.5 runtimes checked with Xcode 26.6 on macOS 26.3.1.
launchd_sim is the first process of a booted Xcode simulator: it plays the role launchd plays on a real device and starts the simulated system's daemons and apps. There is one for each booted simulator, and the simulated processes it starts run on your Mac and use its CPU and memory. Shutting the simulator down ends launchd_sim and everything under it.
launchd_sim at a glance
| launchd_sim | |
|---|---|
| Made by | Apple (part of Xcode simulator runtimes) |
| Type | Simulator process manager |
| Location | /Library/Developer/CoreSimulator/Volumes/[runtime]/Library/Developer/CoreSimulator/Profiles/Runtimes/[name].simruntime/Contents/Resources/RuntimeRoot/sbin/launchd_sim |
| Runs as | your user |
| Can you quit it? | Quitting it shuts down that simulated device abruptly. Shut the device down with Simulator or simctl instead. |
What is launchd_sim?
Each simulator runtime contains a copy of the device's system files in a RuntimeRoot folder, and launchd_sim is in its sbin folder. On this Mac the iOS 26.5 and watchOS 26.5 runtimes each contain one, inside disk images mounted under /Library/Developer/CoreSimulator/Volumes.
When a device boots, CoreSimulator starts its launchd_sim, which then starts the simulated system's services and your app. In Activity Monitor these appear as ordinary processes owned by you, many with names that match iOS daemons.
Is launchd_sim safe?
Yes. It comes from Apple's simulator runtimes installed with Xcode and only runs while a simulator is booted.
Why does launchd_sim use so much CPU and memory?
- Booting a simulator. On boot the simulated system starts dozens of services, which shows as a burst of CPU under launchd_sim's children.
- Several devices booted. Each booted device runs its own launchd_sim and system services. Two or three devices booted at once add up in memory.
- Your app running in the simulator. The app you are testing runs as a Mac process under the simulator, so its own CPU use counts on your Mac.
How much CPU is normal for launchd_sim?
One launchd_sim per booted simulator. Its own CPU use is small; the CPU you see belongs to the processes it started.
None at all when no simulator is booted.
How do you stop simulators from using your Mac's CPU?
- List booted devices. Run
xcrun simctl list devices bootedto see which simulators are running. - Shut them down. Run
xcrun simctl shutdown all, orxcrun simctl shutdown <device>for one device. - See what a simulator is running. In Activity Monitor choose View > All Processes, Hierarchically and expand launchd_sim to see the simulated processes under it.
- Erase a misbehaving device.
xcrun simctl erase <device>erases a device's contents and settings, which gives it a fresh start if its simulated system misbehaves.
When should you worry about launchd_sim?
launchd_sim processes that remain after you think all simulators are closed mean devices are still booted. xcrun simctl shutdown all stops them.
A launchd_sim running from outside a simulator runtime folder would not be Apple's.
How do you check launchd_sim in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type launchd_sim in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every launchd_sim process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'launchd_sim' | grep -v grep
How can Thrum help with launchd_sim?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when launchd_sim is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click launchd_sim in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about launchd_sim
Why are there several launchd_sim processes?
One runs for each booted device. A paired iPhone and Apple Watch simulator, for example, run two.
Does quitting Simulator stop launchd_sim?
Check with xcrun simctl list devices booted. Any device still listed there is running, and xcrun simctl shutdown all ends its launchd_sim.
Sources
- simctl help: run xcrun simctl help in Terminal
- Apple Support: View information about Mac processes in Activity Monitor