Closing the app from task manager does not kill it
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox68 affected)
Tracking | Status | |
---|---|---|
firefox68 | --- | affected |
People
(Reporter: sflorean, Unassigned)
References
Details
Environment:
Device: Google Pixel(Android Q);
Build: Nightly 68.0a1 (2019-04-09);
Steps to reproduce:
- Open one tab in normal browsing.
- Open one tab in private browsing.
- Close Nightly.
Expected result:
The private session is not restored.
Actual result:
The private session is restored.
Notes:
- Not reproducible on Android 8 and 9.
Video: https://drive.google.com/open?id=1ptJMp_CVJItLZGTbVBPoNuNB-ONZrdUw
Comment 1•6 years ago
|
||
I cannot reproduce this behavior using a Pixel 2XL and Android Q.
Comment 2•6 years ago
|
||
Video: https://drive.google.com/open?id=1ptJMp_CVJItLZGTbVBPoNuNB-ONZrdUw
Not publicly visible.
That aside, this might seem like a possible bug in Android Q in that the savedInstanceState isn't cleared when we'd expect it to (swiping the app away in the task switcher).
Is this using the current (second I think) Android Q preview build? If yes, it might be worth filing an issue with Google, though I'd expect they'd want a small demonstration app which could reproduce the issue, which I personally won't be able to provide.
Reporter | ||
Comment 3•6 years ago
•
|
||
(In reply to Jan Henning [:JanH] from comment #2)
Video: https://drive.google.com/open?id=1ptJMp_CVJItLZGTbVBPoNuNB-ONZrdUw
Not publicly visible.
It should be now.
That aside, this might seem like a possible bug in Android Q in that the savedInstanceState isn't cleared when we'd expect it to (swiping the app away in the task switcher).
Is this using the current (second I think) Android Q preview build? If yes, it might be worth filing an issue with Google, though I'd expect they'd want a small demonstration app which could reproduce the issue, which I personally won't be able to provide.
I observed the same behavior with videos, closing, and opening again the browser didn't affect the progress.
Video: https://drive.google.com/open?id=1uAT6Gbklp_aJLMy67E-9QPqTy8kYSb1C
I will update the bug to reflect the new findings.
Comment 4•6 years ago
|
||
I observed the same behavior with videos, closing, and opening again the browser didn't affect the progress.
Same thing happens in the first video - the Google Maps tab appears too fast to be a cold start.
Comment 5•6 years ago
|
||
I think it's possible that removing the app from the task switcher does not actually kill it and so the problem would be with the Android build and not with our app.
To test for this you could try to "Force Stop" the app from System Settings and check if the issue still reproduces.
Reporter | ||
Comment 6•6 years ago
|
||
Tested with the latest Nightly Build and couldn't reproduce again following the same steps as in description. I will close this bug as worksforme.
Assignee | ||
Updated•4 years ago
|
Description
•