Traceline is a good way to see how this happens. We generally name
all of the Chrome threads (base::Thread), but the system is allowed to
create threads of its own. Loads of APIs create threads, along with
the windows worker pool (which we make good use of to help reuse
threads). For example,
Just for the record - Tp prefix stands for Thread Pool, and Tpp
for Thread Pool Private (function).
So yes, these are threads created by the system.
On Thu, Dec 31, 2009 at 10:09 AM, Jim Roskind j...@chromium.org wrote:
I'm pretty sure we name all the threads we can (or at least used to), I
If you do not care about the way threads are run inside a process in
Chromium, you can stop reading now.
Some of our threads are named, while others are not. See below cdb.exe
output for a renderer process:
2:020:x86 ~
1 Id: d98.1588 Suspend: 1 Teb: 7efd8000 Unfrozen Chrome_ChildIOThread
.
On Thu, Dec 31, 2009 at 1:11 AM, Berend-Jan Wever skyli...@chromium.org wrote:
It would be nice if we could name all threads, so you know what you're
looking at.
It would be nice if threads were required to be given a name as part
of creation, perhaps with a central registry to make sure things
I'm pretty sure we name all the threads we can (or at least used to), I
*think* the problem is worker threads in a thread pool, which are started up
and shut down automatically, and aren't named (and don't have message
loops).
When I was doing the work to generate the internal page about:tasks,