New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 710984 link

Starred by 3 users

Issue metadata

Status: Archived
Owner:
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

icons for running android apps not shown in shelf after discards

Project Member Reported by semenzato@chromium.org, Apr 12 2017

Issue description

I am running high-memory pressure experiments, which intentionally create tab discards and app kills, and possibly involve kernel OOM kills.  After running these for a while, my shelf only contains the "circle" icon and the chrome icon, even though I have four or five Android apps running and can switch among those.

I am on ToT as of a few days ago.

Please let me know what logs may be useful.
 

Comment 1 by uekawa@google.com, Apr 13 2017

Cc: khmel@chromium.org

Comment 2 by khmel@chromium.org, Apr 13 2017

Hi, thanks for reporting. If possible /home/user/XXXXXX/log/chrome_XXXXX.log and logcat can be useful. Is any chance I can reproduce this locally (script or test)?
I will try to reproduce today.  The system is still in that state if you want to take a look, I will IM you the IP address.

Comment 4 by khmel@chromium.org, Apr 13 2017

Cc: lhchavez@chromium.org
One strange thing I see is one per 90 seconds
"WARNING:arc_session_manager.cc(209)] Provisioning result was already reported. Ignoring additional result 0."

Does it mean that Android container gets restarted each time?

CC Luis 
chrome
2.4 MB View Download

Comment 5 by khmel@chromium.org, Apr 13 2017

logcat.txt
811 KB View Download
No, that's just an effect of the OOM kills. ArcAppLauncher will report provisioning each time it's launched. Since semenzato@'s experiment is killing it repeatedly, you'll see several log statements for it.

The container as a whole survives this whole exercise.

Comment 7 by khmel@chromium.org, Apr 13 2017

Yes, also see this (logcat is not interrupted). It seems problem comes from restarting AppLauncher. Will test this case. 

Comment 8 by khmel@chromium.org, Apr 13 2017

Owner: khmel@chromium.org
Cc: cylee@chromium.org
This is actually pretty easy to reproduce, and tt appears that the AppLauncher is killed before other Android apps are.  Is this the correct behavior, or are we assigning the wrong kill priority to it?

Comment 11 by cylee@google.com, Apr 13 2017

Yes as #10 pointed out, the process org.chromium.arc.applauncher is not deemed as "important process" by Chrome so it's not assigned oom_score_adj -1000
Chrome has no knowledge of what Android apps are "important" and what are not. 

Anybody from ARC++ team want to add a android:persistent="true" to ArcAppLauncher as well?

Comment 12 by khmel@chromium.org, Apr 13 2017

Thank you @cylee for your comment. I will take care about it.

Comment 13 by khmel@chromium.org, Apr 13 2017

Labels: M-58

Comment 14 by khmel@chromium.org, Apr 26 2017

Cc: yusukes@chromium.org
Status: Fixed (was: Untriaged)
This was fixed by yusukes@'s ag/2148956
I wasn't aware of this bug, but yes, it should be fixed now. nyc-arc M58+ and mnc-arc M60+ will be okay.

Will probably merge this into mnc-arc M59 too since the other issue ( crbug.com/706048 ) is marked as P1 M58. Merging the CL to mnc M58 is probably too late but doing so to mnc M59 is probably okay.

khmel@ Trying to verify this bug. Could you provide verification steps?

Comment 17 by khmel@chromium.org, May 19 2017


Try to run apps with heavy memory consumption. At some point you should see that some apps are killed by OOM. In any case shelf should correctly display list of apps.

Probably  semenzato@ or yusukes@ can provide more details here.
If you have a dev-mode device, please try https://bugs.chromium.org/p/chromium/issues/detail?id=706048#c76 (please note that you need to reboot your device after step #3 to reflect the swap setting change.)

At some point, lots of tab/app kill logs will show up in ui.LATEST, but the icons should be still there.

Comment 19 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment