-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Bug] Fenix doesn't handle content process dying #1577
Comments
I think the problem here is that Fenix doesn't handle |
Submitted an a-c patch here: mozilla-mobile/android-components#3170 |
Amazing work, thank you 💯 |
This appears to have been fixed in v1.3.0-rc1, but regressed in v1.3.0-rc2 and 3 (or at least the symptom has). |
@stuarthenderson could you give more details about what you're seeing in v1.3.0-rc3 related to this bug? |
Same symptom as before. I'd been using rc1 since it appeared on taskcluster without issue. Yesterday i tried rc2 and noticed one of my tabs got set to "about:blank". It happened again an hour or two later. I noticed rc3 today and tried that, but it happened again. Happens when i navigate away from Preview for a bit (using other apps) and when you go back occasionally one or more of the "tabs" are at "about:blank". I think each time it was the last used tab that goes to a:b. |
Did you open the tab? I just had one case where two of four tabs became about:blank, then restored when I opened the tab. |
Ah! You're right. It does eventually recover when you select the tab. Thanks! |
I think what you might be seeing is a variant of #3846. Currently the tabs tray does not seem to update automatically whenever the tabs/ |
Still seeing .. This or something like this on occasion. Usually, after I open a bunch of new tabs (click a link and open in new tab), switch tabs a few times and then switch apps..When I come back to fenix, it has been killed by this os and I get this: The tabs are all about:blank with no history in them |
Logged a new issue: #5478 |
Steps to reproduce
Simulate device killing content process:
adb shell
$ run-as org.mozilla.fenix.debug
:tab
process id:$ ps -A | grep org.mozilla.fenix.debug:tab
$ kill -9 <PROCESS ID>
Note: This is really common, especially on lower-end android devices.
Expected behavior
Pages refreshes and keeps state as much as possible
Actual behavior
Fenix navigates to about:blank
Device information
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: