<h2><imgsrc="../../images/desktop-applets-images/processcontroller-icon_64.png"alt="processcontroller-icon_64.png"width="64"height="64"/>ProcessController (Controlador de procesos)</h2>
<p><imgsrc="../images/processcontroller-images/applet.png"alt="ProcessController applet"style="float:left;margin: 0 4em 0 0"/>The primary task of ProcessController applet is to show CPU(s) activity and amount of used memory. It allows monitoring of individual processes, change their priority, and kill them if the program freezes. In multiprocessor environments it allows you to disable individual processors/cores. When <ahref="../tracker.html"><spanclass="app">Tracker</span></a> or <ahref="../deskbar.html"><spanclass="app">Deskbar</span></a> crashes you can run it again from ProcessController's menu.</p>
<p>Indicators on the left shows each CPU usage, while the bar on the right shows the memory consumption. Remember that the number of indicators depends on the number of processors in the computer.</p>
<p>If not yet running, launching ProcessController will ask if it should open in window mode or live in the Deskbar tray. In window mode you're able to resize the icon by resizing the window and use the <ahref="../gui.html#replicants">Replicant</a> handle to drag it to the Desktop.<br/>
Wherever it's installed, it's operated via a right-click context menu.<br/>
To remove the applet again from your tray, uncheck <spanclass="menu">Live in the Deskbar</span> in its context menu.</p>
<h2>Quit an application</h2>
<divclass="box-stop">Remember that closing an application can cause data loss and additionally the system may stop working reliably.</div>
<imgsrc="../images/processcontroller-images/quit.png"alt="ProcessController - Quit an application"/>
<p>To quit an application just choose it's name from the <spanclass="menu">Quit an application</span> menu. This is a clean way to close app, just like when you would click the close button. There are some teams that cannot be quitted this way, mostly system processes.</p>
<divclass="box-warning">Memory usage monitoring can be very inaccurate.</div>
<p>This menu allows you to monitor memory usage of different teams in your system. Next to the team's name there are two columns: first with memory amount reserved for write, while the second shows all memory including read-only space (shared libraries for example).</p>
<p>The first row <spanclass="menu">System resources & caches...</span> shows total amount of memory used by system and all applications. The length of the blue bar is based on total physical memory in your computer. The next rows show memory used by each process. Please note that the length of the bar is based only on the used part of memory.</p>
<table>
<tbody>
<tr><tdstyle="width:20px;height:20px;background:#1414E7"></td><tdstyle="width:10px"></td><td>Memory used only by given application (with write access)</td></tr>
<tr><tdstyle="height:20px;background:#A4A4F5"></td><td></td><td>Memory including read-only space (can be shared with other applications)</td></tr>
<divclass="box-stop">Everything in this menu can cause data loss and system instability.</div>
<p>This menu allows you to change thread priorities, kill processes or debug them.<br/>
At the first level you see team names, when you click on it, you can kill the whole team. The dark-blue part of the bar is spent in kernel code, the light-blue part in user code, the green part in the idle thread(s). A bar completely filled with blue means that the team is using all processing power.<br/>
At the second level there are particular threads. By clicking them you can debug or kill them. A bar completely filled with blue means that the thread is using completely one processor/core.<br/>
The last level of the menu allows you to change a thread's priority.
