| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Android we explicitly allow the OS to kill Chrome's background
renderers when under memory pressure and we don't try to control the
number of renderers ourselves.
The process limit logic in content causes process sharing
between unrelated tabs when the number of renderer process hosts
(not the number of actual live processes) is too high. Because on
Android the system adjusts the number of actual live processes for us,
we don't want to limit the number of process hosts or to ever share
renderers between unrelated tabs.
This patch:
- disables the renderer process host limit on Android. If not
overridden, ShouldTryToUseExistingProcessHost() will always return
false.
- drops the logic that sets the renderer limit based on the number of
declared renderer services
BUG=325842
Review URL: https://codereview.chromium.org/356453003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@284095 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Android we can get a second request to start the browser while
the an asynchronous request is in progress. Since the second
request may be synchronous, we may have switch to completing
initialization synchronously. This patch handles this by tracking
which initialization tasks have been run, and running the remaining
initialization tasks.
BUG=260574
Review URL: https://chromiumcodereview.appspot.com/22691002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219795 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
This CL adds support for easily doing multiple asynchronous startups
where every startup request can get their own callback executed. This
makes the logic in at the caller very simple by for example extracting
away usage of AndroidBrowserProcess and catching ProcessInitException.
BrowserStartupConfig is renamed to BrowserStartupController, since it
now does more than just keep the configuration. The
BrowserStartupController is called from native when the native startup
is complete. It keeps an ordered list of caller's callbacks which will
all be called when initialization is finished. If initialization has
already been completed before the async startup request is called,
the callback is called immediately.
The first users of this are content shell and chromium testshell.
BUG=260574
Review URL: https://chromiumcodereview.appspot.com/22272006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218562 0039d316-1c4b-4281-b951-d872f2087c98
|
