--renderer-process-limit

[MilesAhead]

After experimenting a bit with this setting, it seems that is somehow
remembers the last setting. For example I'm using Chromium 21.0.1156.0
and if I started with a blank page, I might have a dozen chrome.exe
showing in task manager. So I run it with the param --renderer-
process-limit=4

Now when opening a blank page I only have 7 copies of chrome.exe. But
here's the kicker. I run chrome with no command line switch and open a
blank page. Still only 7 instances of chrome.exe.

After searching the web it seems there was an old built in max of
42(apparently the answer to the universe and everything.) I run it
with --renderer-process-limit=42. Now when I go back to using with no
switch I get the original behavior. So my question is wouldn't it be
a good idea to have a number, such as --renderer-process-limit=-1 or --
renderer-process-limit=0 to indicate to the program to reset the
default?

[Simon Hong]

I'm running r140641 on Linux with aura.

This option works well to me.

With limit=2, only two renderer process are forked regardless of the number of tab.

Without limit-2, more renderer is forked.

--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-discuss

--
======================================

Simon Hong

"Secret of success is consistency to purpose"

[MilesAhead]

The point is not that it doesn't limit the processes. It does. The
question was how to restore the default setting. So far the only way
I've found is guess at the number, such as entering 42, or copying
over all my user settings from a saved folder. It would be nice if
there was a setting such as 0 or -1 to restore default.

On Jun 6, 2:07 am, Simon Hong <simon.hon...@gmail.com> wrote:
> I'm running r140641 on Linux with aura.
> This option works well to me.
> With limit=2, only two renderer process are forked regardless of the number
> of tab.
> Without limit-2, more renderer is forked.
>
>
>
>
>
>
>
>
>
> On Wed, Jun 6, 2012 at 5:32 AM, MilesAhead <miles__ah...@hotmail.com> wrote:
> > After experimenting a bit with this setting, it seems that is somehow
> > remembers the last setting. For example I'm using Chromium 21.0.1156.0
> > and if I started with a blank page, I might have a dozen chrome.exe
> > showing in task manager.  So I run it with the param --renderer-
> > process-limit=4
>
> > Now when opening a blank page I only have 7 copies of chrome.exe.  But
> > here's the kicker. I run chrome with no command line switch and open a
> > blank page.  Still only 7 instances of chrome.exe.
>
> > After searching the web it seems there was an old built in max of
> > 42(apparently the answer to the universe and everything.)  I run it
> > with --renderer-process-limit=42.  Now when I go back to using with no
> > switch I get the original behavior.  So my question is wouldn't it be
> > a good idea to have a number, such as --renderer-process-limit=-1 or --
> > renderer-process-limit=0 to indicate to the program to reset the
> > default?
>
> > --

> > Chromium Discussion mailing list: chromium-disc...@chromium.org

[Michael Nordman]

It'd be good to file a bug about this insidious'ness.
https://code.google.com/p/chromium/issues/entry

> Chromium Discussion mailing list: chromium...@chromium.org