Comment #25 on issue 6844 by [email protected]: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detail?id=6844
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=32264
------------------------------------------------------------------------
r32264 | [email protected] | 2009-11-17 18:41:26 -0800 (Tue, 17 Nov 2009) |
4 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/process_util_posix.cc?r1=32264&r2=32263
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/child_process_launcher.cc
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/child_process_launcher.h
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/extension_browsertest.cc?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/extension_host.cc?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/browser_render_process_host.cc?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/browser_render_process_host.h?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/mock_render_process_host.cc?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/mock_render_process_host.h?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_process_host.h?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/tab_contents/tab_contents.cc?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/visitedlink_event_listener.cc?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/visitedlink_master.cc?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/visitedlink_master.h?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/visitedlink_unittest.cc?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/zygote_host_linux.cc?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/zygote_host_linux.h?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/chrome.gyp?r1=32264&r2=32263
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/notification_type.h?r1=32264&r2=32263
Launch processes asynchronously so as not to block the UI thread. For now,
renderer only, I'll take care of plugin/worker/utility processes in a
followup change. (relanding 32203)
BUG=6844
Review URL: http://codereview.chromium.org/397031
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
