This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 473
Recover when content process gets killed #3310
Labels
<engine-gecko>
Component: browser-engine-gecko
🌟 feature
New functionality and improvements
🐉 Fenix
Feature needed for Fenix
P1
Milestone
Comments
pocmo
added
🌟 feature
New functionality and improvements
<engine-gecko>
Component: browser-engine-gecko
🐉 Fenix
Feature needed for Fenix
needs:gv
To implement/fix this we need a new API in GeckoView
labels
Jun 7, 2019
pocmo
added a commit
to pocmo/android-components
that referenced
this issue
Jul 16, 2019
…ly recover and restore if content process is killed.
pocmo
added a commit
to pocmo/android-components
that referenced
this issue
Jul 16, 2019
…ly recover and restore if content process is killed.
pocmo
added a commit
to pocmo/android-components
that referenced
this issue
Jul 16, 2019
…ly recover and restore if content process is killed.
Blocked: The added GeckoView API was backed out due to regressions :( |
This is no longer blocked on nightly GV. The |
pocmo
added a commit
to pocmo/android-components
that referenced
this issue
Jul 23, 2019
…ly recover and restore if content process is killed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
<engine-gecko>
Component: browser-engine-gecko
🌟 feature
New functionality and improvements
🐉 Fenix
Feature needed for Fenix
P1
Fenix issue: mozilla-mobile/fenix#1577
GeckoView bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1557096
Currently we see
onCrash()
getting called for aGeckoSession
- but we have no clue whether that is a crash or whether the content process just got killed by Android to reclaim some resources.We can handle crashes (via
lib-crash
) and allow the user to restore manually - but we need a way to know whether a call toonCrash()
was just for a process kill so that we can auto-restore.┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: