Use the process monitor
See how Choro and its related processes are using memory and CPU.
Last updated 16 September 2026
See how Choro and its related processes are using memory and CPU.
Before you start
Open the monitor while the workload you want to investigate is present. Record what is running so a resource reading has useful context.
Read Choro’s own memory separately from related processes. Refresh after a workload changes, and include that workload when reporting a performance issue.
Step by step
Open Settings → Process monitor and read the Choro, Related, and CPU summary.
Read the measurement note below the summary. Physical footprint includes compressed and swapped memory; a fallback resident-memory reading is a different measurement.
Inspect Inside Choro to see the allocation types contributing to the application’s own memory.
Scroll through Related processes. Choro groups them by project and agent when ownership can be identified, with larger groups first.
Use Refresh to take another snapshot after the activity changes. Compare like-for-like workloads rather than treating one temporary peak as a leak.
If you need to stop work, return to its conversation, terminal, or service controls and stop the intended task there. Then refresh the monitor to observe the effect.
For a performance report, include the workload, approximate duration, memory and CPU readings, and whether the usage settles after the work finishes.
What to expect
You can distinguish the app’s own resource use from related agents, web content, terminals, and scripts.
Troubleshooting and useful details
The screenshot is one live demo reading, not a recommended limit or a performance benchmark. Unidentified ownership does not prove a process is unrelated. A high value during active generation needs different interpretation from steady growth while idle.