Processes
The Process Monitor lists every process running under your account: website workers, app servers, containers, cron jobs, and terminal sessions. It refreshes every few seconds.
Resource Usage answers "how much?"; this page answers "what is doing it?". When your memory or process count nears its limit, this is where you find the cause.
Each row shows the process ID, its parent's ID, the user it runs as, memory, start time, and the full command line. Select a column to sort by it, or pause the refresh to read a list that changes quickly.
RSS is what counts against your memory limit. VSZ is a theoretical number.
Stop a process
Select one or more processes and send a signal:
| Signal | Use |
|---|---|
| SIGTERM | Send this first. It asks the program to exit and gives it time to finish. |
| SIGKILL | Only when the program ignored SIGTERM. It ends the process immediately, and the process can't refuse. |
| SIGHUP, SIGINT, SIGUSR1, SIGUSR2 | For a program that gives them a meaning, e.g. "reload the configuration". |
An app server starts again at the next request, and a container follows its restart policy. If a supervised process keeps misbehaving, fix it, or stop it on its own page.
A process can end before the signal reaches it; the panel then reports that it didn't find the process. With a 3-second refresh on a busy account, that's normal, not an error.