New issue
Advanced search Search tips

Issue 868546 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Cannot reliably reopen previous session when re-opening chrome.

Reported by c933...@gmail.com, Jul 27

Issue description

Steps to reproduce the problem:
1. Use Chrome for Android in an Android device with limited free storage (constantly less than 100MB and sometimes down to 0 requiring manual cleanup)
2. Use Chrome for android with the usage habit of opening a new tab and never closing any of then when the user want to click on a link
3. Continue doing so for several weeks or months

What is the expected behavior?
Tabs should be restored every time user enter Chrome

What went wrong?
Every once in a while, when user enter chrome, it would show up a white screen for a few minutes, then come up.with a warning saying it is now crashed. Then when user try to relaunch in this situation, there are about 1% probability that it would fail again, and then in another about 10% probability that ultimately the chrome would show a new session with only 1 tab for the homepage instead of showing the previous session.

Did this work before? No 

Chrome version: 64.0.3282.137  Channel: stable
OS Version: 
Flash Version: 

Keep on randomly encountering something similar for years in the past
 
 تفعيل الملف
946401778754875
62.0 KB View Download
Labels: Needs-triage-Mobile
Cc: chelamcherla@chromium.org
Components: UI>Browser>Sessions
Labels: Needs-Feedback Triaged-Mobile
Unable to reproduce this issue on reported version 64.0.3282.137 and latest stable 68.0.3440.70.

@Reporter: Could you please provide device details including OS version.Also you are using out dated version of google chrome. Please verify by updating Chrome to latest stable #68.0.3440.70. Also please provide 16digit crash id from chrome://crashes. This would help in better triaging of the issue.

Thanks!

OS version: Android 8.0.0
And I see no 16 digit crash id in chrome://crashes. There are only 8-digits alphanumeric ids
Project Member

Comment 5 by sheriffbot@chromium.org, Aug 2

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
ah, I need to send them. After sending them, id for the most recent ten reports are:
46bb30b89551a6b9 
12c08a0dba74e0ff 
1f6ba6af36915d82 
391b9485050fa6fd
ec1332e38585b98c 
cd33a3c9021aeb23 
e7206c394c8a7eb1 
406dcbac94476dfa 
84098499f90a39ed 
c3e7d7ecfa6d771f
I am not sure if they include the crash that were described in my issue
Another similar situation occurs again today:
Related bug reports:
23760ad720fe8676
32e0521380509b43
d690613aa88nne89
5ae45613519d117a
I have encountered another similar situation again. No bug report was generated when this situation occurs, however the two startup after the situation was longer than usual and crashed. See bug report:
3434238903e84816
3760e33d9bbaa016
Same situation happen again, bug reports:
4fd04afd860d31fd
140035d11864b41f
acd1c4bba7a45c96
bece8d6935504b3f
Happened again
No crash report have been generated by chrome during the entire process and with all the crashed this time
how many times more would I need to experience this process before the bug can be fixed?
again.
It have occurred again. When cam the problem be fixed?
Can anyone help?
Face the same problem again
Encounter same problem again
Encounter same problem AGAIN
It happened to me again. How to fix it?
It happened again
It happened again.
It happened again. x n
It happened again. for the uncountable amoutn of times
Again.....
Again....

Sign in to add a comment