New issue
Advanced search Search tips

Issue 655160 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Monochrome and standalone WebView run multiprocess renderers inconsistently on 64-bit

Project Member Reported by torne@chromium.org, Oct 12 2016

Issue description

On a 64-bit device when multiprocess is enabled:

1) if WebView is implemented by Monochrome, renderer processes are 32-bit, because monochrome's APK specifies that it prefers to be run in 32-bit mode to reduce Chrome memory usage.

2) if WebView is implemented by the standalone APK, renderer processes are 64-bit, because the flag isn't set in the webview APK.

This means that we'll get different memory usage, performance, startup time and bugs in multiprocess mode depending on which implementation is being used, even if they're the exact same version. This probably isn't desirable - we should add the prefer 32-bit flag to the WebView APKs as well, since one of the benefits of multiprocess is the ability to run the renderer in 32-bit to save memory even when webview is being used by a 64-bit app.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Oct 14 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d9afdaaf5198350a06c484e4b7fbb3de50e3914a

commit d9afdaaf5198350a06c484e4b7fbb3de50e3914a
Author: torne <torne@chromium.org>
Date: Fri Oct 14 10:20:42 2016

Set 32-bit ABI flag in WebView manifest.

In multiprocess mode we currently want to run WebView renderers as
32-bit on 64-bit devices for memory savings. This is already the case
for Monochrome, but the standalone WebView was not setting the
appropriate flag in its manifest; add it here.

BUG= 655160 

Review-Url: https://codereview.chromium.org/2414333002
Cr-Commit-Position: refs/heads/master@{#425288}

[modify] https://crrev.com/d9afdaaf5198350a06c484e4b7fbb3de50e3914a/android_webview/apk/java/AndroidManifest.xml

Comment 2 by torne@chromium.org, Oct 14 2016

Status: Fixed (was: Assigned)

Sign in to add a comment