[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Comment #25 on issue 6844 by bugdro...@chromium.org: 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 -

[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Comment #23 on issue 6844 by bugdro...@chromium.org: 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=32205 -

[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Comment #21 on issue 6844 by tony.chromium: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detail?id=6844 agl also speculated that some slowness might be due to having chrome-sandbox, which is a separate binary. if the disk is busy (say

[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Comment #20 on issue 6844 by j...@chromium.org: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detail?id=6844 Agreed. That's what my patch does (in a way that works for all platforms). I'm going to extend it to plugin/worker/utility pr

[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Comment #19 on issue 6844 by e...@chromium.org: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detail?id=6844 Hm, we should make that async too. :D -- You received this message because you are listed in the owner or CC fields of this iss

[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Comment #18 on issue 6844 by j...@chromium.org: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detail?id=6844 From what Adam explained, it's forked initially and we don't block on it. But the first time we need to launch a renderer pro

[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Comment #17 on issue 6844 by e...@chromium.org: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detail?id=6844 I'm surprised that the browser blocks on the zygote process starting. I thought we fork and forget about it. -- You received

[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Comment #16 on issue 6844 by j...@chromium.org: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detail?id=6844 I talked to Tony and Adam today, and the best explanation that comes up for why Linux is slow to start the first renderer is be

[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Comment #12 on issue 6844 by a...@golang.org: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detail?id=6844 What I see is a bimodal distribution. Many people start in 50ms, but a second group take much longer (nearly a second). I can hy

[chromium-bugs] Re: Issue 6844 in chromium: Consider starting renderer processes from a background thread

Updates: Status: Started Owner: j...@chromium.org Cc: tony.chromium e...@chromium.org Labels: -Pri-3 Pri-2 Comment #10 on issue 6844 by j...@chromium.org: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detai