New issue
Advanced search Search tips

Issue 593956 link

Starred by 1 user
Status: WontFix
Owner:
klo...@chromium.org
Closed: Mar 2016
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

sandboxed_process cannot be cached when com.android.chrome is at Foreground

Reported by qdeng.nv...@gmail.com, Mar 10 2016 
Steps to reproduce the problem:
1. On Nexus 9, open chrome browser, and open a few tabs. I used this webpage(360gigapixels.com/tokyo-tower-panorama-photo/)

2. Connect the device to a host machine and type in the command "adb shell dumpsys meminfo" in terminal.

What is the expected behavior?
Some of the sandboxed_process should be cached. On Nexus 5 (same chrome and android version as Nexus 9), it works fine.
(Please see file "nexus5_meminfo")

What went wrong?
But on Nexus 9, when chrome browser runs at the foreground, the sandboxed_process cannot be cached. (Please see the file "nexus9_chrome_foreground")

Only when I put chrome browser in the background, the chrome browser and sandboxed_process can be cached.

Did this work before? N/A 

Chrome version: 48.0.2564.95  Channel: n/a
OS Version: 6.0.1
Flash Version: Shockwave Flash 20.0 r0
nexus5_meminfo
7.7 KB View Download
nexus9_chrome_foreground
5.3 KB View Download
nexus9_chrome_background
5.2 KB View Download

Comment 1 by qdeng.nv...@gmail.com, Mar 11 2016 

The harm of this issue is that some other apps could be killed (eg. google music player)

Because if sandboxed_processes are in "cached", their oom_adj is high that they will be killed first. But if they cannot in "cached", they might be killed when the oom_adj is low, thus other apps having the similiar oom_adj value could be killed too.

Comment 2 by ppolise...@chromium.org, Mar 14 2016

Owner: klo...@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by klo...@chromium.org, Mar 14 2016

Status: WontFix (was: Assigned)
Please file a bug to Android. sandboxed_process is isolated Android service.

Comment 4 by qdeng.nv...@gmail.com, Mar 14 2016 

Thank you!

I filed an android bug:
https://code.google.com/p/android/issues/detail?id=203847
►

Sign in to add a comment