It's always disabled in Chrome. It's all in the source code. See [1] line ~416.
You can use Google Code Search to grep the code more quickly. For
instance, if you search for single_process, you'll end up on [2] and
oh look at the first result!
[1]
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/chrome_dll_main.cc?view=markup
[2]
http://www.google.com/codesearch?hl=enq=single_processexact_package=http%3A%2F%2Fsrc.chromium.org%2Fsvn%2Ftrunk%2Fsrc
On Mon, Jun 1, 2009 at 12:20 PM, vijay tec...@gmail.com wrote:
The --single-process command-line switch does not seem to be working
with Chrome 2.0. I'm running the latest released version of 2.0.172.28
on Windows XP and even when using the switch, Chrome still starts up
with 2 processes. Then, when I go to a page with a plugin (NPAPI), it
creates a brand new process. Am I doing something wrong or did
something change with --single-process?
Thanks in advance,
Vijay
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---
