The "Threads" page shows you information about the additional threads that
&xwp; currently has running in the WPS process. This might be of interest
for debugging purposes and bug reports.
Each line in this container shows you the internal thread name,
which is only used by &xwp; to be able to identify threads by means other
than an arbitrary numer.
The "TID" value is the "thread ID" of the respective thread (which is unique
within the WPS process). The "Priority" value is the respective thread's priority:
the high byte can be a value of 1 through 4 (signalling the priority class: idle,
regular, time-critical, or forground server),
while the low byte shows the priority "delta" within a priority class.
(See "Processes and threads" for details.)
&xwp; may start the following threads on your system:
- NotifySentinel, RefreshFindFolder, RefreshNotificationPump:
these are running if you enabled "replace folder auto-refresh" on the
"Features" page and are responsible for watching the file system in the background.
- Party: The &xwp; "Party" thread is responsible for multimedia,
such as playing system sounds.
- Worker: See
"The Worker thread" for details.
- Bush: The &xwp; "Bush" thread is asleep most of the time,
but suddenly wakes up for certain cosmetic, yet high-priority tasks which require
immediate attention, such as displaying the &xwp; boot logo.
- Wimp: another idle-time thread which awakes only every few minutes
to perform some memory cleanup and such things.
- File: The &xwp; "File" thread becomes active when &xwp;
is doing file operations, such as moving files to the trash can or deleting files.
- &xcenter;: Since each
&xcenter;
is running on its own thread, you will
see one such thread for each open &xcenter;.
- PulseWidgetCollect: this is only visible if you have the
"Pulse" widget
running in an open &xcenter;. The pulse widget starts a second thread
for getting CPU usage information from the &os2; kernel in order not to be
blocked out if some application monopolizes the PM single input queue.