If you look at a lot of Mac executables, you find that the system can create threads in response to same API calls. On the copy of Chrome I'm currently running, I seeing one renderer with 5 threads and another with 6. At quick glance the extra are the OS doing some extra work in response to api calls. TVL
On Sat, Jun 20, 2009 at 7:39 PM, n179911 <[email protected]> wrote: > > From this post > http://blog.marcchung.com/2008/09/05/chromes-process-model-explained.html, > it said > Each Renderer process has two threads: one Render thread–which renders > web pages, and one IPC thread–which transports data in a thread-safe, > non- blocking manner between the Render thread and an IPC counterpart > sitting in the Browser process. The Renderer process manages 1 IPC > thread and 1 Render thread. > > But when i see that ActivityMoniter on MacOSX, it has 3 threads: > > 262 Chromium john 0.0 3 32.77 MB 974.34 > MB Intel > 189 Chromium john 0.4 16 65.57 MB 1.03 GB > Intel > 307 Chromium john 1.3 3 51.77 MB 992.93 > MB Intel > 295 Chromium john 0.0 3 56.07 MB 992.88 > MB Intel > > Can you please tell me what is the 3rd thread? > > Thank you. > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
