What is lldb-rpc-server, and why is it using memory or CPU?
Last reviewed: 19 November 2026. Path and code signing identifier checked with Xcode 26.6 on macOS 26.3.1.
lldb-rpc-server is part of Xcode's debugger: it runs LLDB, the debugger engine, in its own process and lets Xcode call LLDB's programming interface through remote procedure calls. It works while you debug, loading symbols, evaluating expressions and stepping through code, and its memory grows with the size of the app being debugged. It ends when the debugging session ends.
lldb-rpc-server at a glance
| lldb-rpc-server | |
|---|---|
| Made by | Apple (part of Xcode, LLDB debugger) |
| Type | Debugger server |
| Location | /Applications/Xcode.app/Contents/SharedFrameworks/LLDBRPC.framework/Versions/A/Resources/lldb-rpc-server |
| Runs as | your user |
| Can you quit it? | Yes, but the debugging session it serves ends and the app being debugged may be stopped. |
What is lldb-rpc-server?
LLDB is the debugger in Xcode. The lldb man page describes it as a debugger built from reusable components of the LLVM project, such as the Clang expression parser. lldb-rpc-server ships in Xcode's LLDBRPC.framework, carries the signing identifier com.apple.lldb-rpc-server, and exposes LLDB's API (the SB API) as remote procedure calls, so the debugger runs outside the Xcode process.
Keeping the debugger separate means a problem inside LLDB does not take Xcode down with it, and the debugger's memory is counted against lldb-rpc-server rather than Xcode.
Is lldb-rpc-server safe?
Yes. It is inside Xcode.app, signed by Apple, and runs only while Xcode is debugging.
Why does lldb-rpc-server use so much memory and CPU?
- Loading symbols for a large app. To show variables and call stacks, the debugger reads debug information for the app and its frameworks. Large apps with many dependencies mean more symbols in memory.
- Evaluating expressions. Commands such as
poandexpression, and the variables view, compile and run code in the context of the paused app. - Breakpoints that fire often. Breakpoints with conditions or actions in code that runs many times make the debugger stop, evaluate and resume repeatedly.
- Long debugging sessions. Keeping a session open for a long time, with many expressions evaluated, adds to what the debugger keeps in memory.
How much memory is normal for lldb-rpc-server?
Present only while a debug session is active. Bursts of CPU when the app stops at a breakpoint or you inspect variables are normal.
Memory of a few hundred megabytes or more is typical for large apps, because of the debug information it loads.
How do you keep lldb-rpc-server light?
- Stop debugging when you are done. Click the Stop button in Xcode or press Command-Period. The debugging session ends and so does its server.
- Use conditional breakpoints sparingly. Move breakpoints with conditions out of hot loops, or disable them when you do not need them.
- Run without the debugger. To measure performance or leave an app running, edit the scheme and turn off Debug executable in the Run action, or launch the built app directly.
- Quit a stuck server. If lldb-rpc-server stays busy after the session ended, quit it in Activity Monitor. Xcode starts a new one for the next session.
When should you worry about lldb-rpc-server?
lldb-rpc-server that keeps running and using CPU after you stop debugging and close the project is unusual; quitting Xcode ends it.
A process with this name outside Xcode.app should be checked with codesign -dv.
How do you check lldb-rpc-server in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type lldb-rpc-server in the search field. The Memory tab shows its Memory. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every lldb-rpc-server process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'lldb-rpc-server' | grep -v grep
How can Thrum help with lldb-rpc-server?
Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory, so you can see how much lldb-rpc-server holds and whether the Mac is short of memory. An optional alert tells you when memory pressure turns critical. Click lldb-rpc-server 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 lldb-rpc-server
Is lldb-rpc-server the same as debugserver?
No. lldb-rpc-server runs LLDB for Xcode; debugserver is a separate helper that controls the process being debugged on the Mac or a simulator.
Why does memory use go up while I debug?
The debugger loads debug symbols for the app and every framework it uses, and keeps results of expressions you evaluate.
Sources
- lldb(1) man page: run man lldb in Terminal (installed with Xcode)