--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview-dev+unsub...@chromium.org.
To post to this group, send email to android-webview-dev@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/android-webview-dev/CAGD3t5Gtnrrqqj2s0-JOOscocb5amkEkr8cK-271tAY_ZHe1%2Bw%40mail.gmail.com.
Multiprocess became the default in Android O. It was a developer setting in N (defaulting to off), and before that it was not supported. Thus, the vast majority of all devices use a single process webview.Toby.On Thu, Jun 1, 2017 at 2:11 PM, François Doray <fdo...@chromium.org> wrote:The traces obtained on this dashboard [1] show android_webview running in a single process. Do all/some users run android_webview in a single process?The perf regression is likely due to the fact that the renderer is inside the browser process. I could fix it, but I want to make sure that users actually hit this scenario.Thanks![1] Click on the perf regression on the graph. Then, in the popup, click on the "Trace" link. Observe the "Chrome_InProcRendererThread".
--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview...@chromium.org.
To post to this group, send email to android-w...@chromium.org.
Is there a way to tell from aw_content_browser_client.cc whether android_webview is running in a single process? Should I check the kSingleProcess or kWebViewSandboxedRenderer command line switches?
On Thu, Jun 1, 2017 at 9:14 AM Toby Sargeant <tobi...@google.com> wrote:
Multiprocess became the default in Android O. It was a developer setting in N (defaulting to off), and before that it was not supported. Thus, the vast majority of all devices use a single process webview.Toby.On Thu, Jun 1, 2017 at 2:11 PM, François Doray <fdo...@chromium.org> wrote:The traces obtained on this dashboard [1] show android_webview running in a single process. Do all/some users run android_webview in a single process?The perf regression is likely due to the fact that the renderer is inside the browser process. I could fix it, but I want to make sure that users actually hit this scenario.Thanks![1] Click on the perf regression on the graph. Then, in the popup, click on the "Trace" link. Observe the "Chrome_InProcRendererThread".
--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview-dev+unsub...@chromium.org.
To post to this group, send email to android-webview-dev@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/android-webview-dev/CAGD3t5Gtnrrqqj2s0-JOOscocb5amkEkr8cK-271tAY_ZHe1%2Bw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/android-webview-dev/CAGD3t5EGw7yvDo_MD5vu1TZoC94Z-6iyeE-rOUdCDXdz4VLgsw%40mail.gmail.com.To unsubscribe from this group and stop receiving emails from it, send an email to android-webview-dev+unsub...@chromium.org.
To post to this group, send email to android-webview-dev@chromium.org.
kSingleProcess is the right flag. kWebViewSandboxedRenderer isn't propagated to child processes.On Thu, Jun 1, 2017 at 2:27 PM, François Doray <fdo...@chromium.org> wrote:
Is there a way to tell from aw_content_browser_client.cc whether android_webview is running in a single process? Should I check the kSingleProcess or kWebViewSandboxedRenderer command line switches?
On Thu, Jun 1, 2017 at 9:14 AM Toby Sargeant <tobi...@google.com> wrote:
Multiprocess became the default in Android O. It was a developer setting in N (defaulting to off), and before that it was not supported. Thus, the vast majority of all devices use a single process webview.Toby.On Thu, Jun 1, 2017 at 2:11 PM, François Doray <fdo...@chromium.org> wrote:The traces obtained on this dashboard [1] show android_webview running in a single process. Do all/some users run android_webview in a single process?The perf regression is likely due to the fact that the renderer is inside the browser process. I could fix it, but I want to make sure that users actually hit this scenario.Thanks![1] Click on the perf regression on the graph. Then, in the popup, click on the "Trace" link. Observe the "Chrome_InProcRendererThread".
--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview...@chromium.org.
To post to this group, send email to android-w...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/android-webview-dev/CAGD3t5Gtnrrqqj2s0-JOOscocb5amkEkr8cK-271tAY_ZHe1%2Bw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview...@chromium.org.
To post to this group, send email to android-w...@chromium.org.