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

Issue 602653 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Lost incognito tabs

Project Member Reported by klo...@chromium.org, Apr 12 2016

Issue description

Seem happened couple of times recently in Chrome dev. Don't know the exact repro steps.

I noticed "Close all incognito tabs" notification is still there.

Open Chrome Dev, no incognito tabs.

I did "adb shell ps" once. Still a lot live sandboxed_processXX. So it means Chrome Dev should not be killed due to oom neither.

File the bug to monitor as I believe I only saw this recently in Chrome Dev.
 

Comment 1 by vabr@chromium.org, Apr 17 2016

Components: UI>Browser>Incognito
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 13 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
Haven't seen this, so closing this out.

If Chrome isn't in the foreground, I think the renderers and browser process can be at the same priority, so Android "could" kill the browser process first.  The incognito notification doesn't get cleared during a crash since we don't actually know if we can restore incognito tabs until the next cold start to see if the instance state was saved with the encryption key.

Sign in to add a comment