1654570 - Telemetry probe for content processes killed by Android due to resource reclamation

Status: RESOLVED FIXED

(GeckoView Graveyard :: Sandboxing, enhancement, P3)

Description

[(No longer employed by Mozilla) Aaron Klotz]

We'd like to monitor process kills in GV so that we have an idea of how Android is behaving when it kills content processes to free up resources.

One problem here is that we need to be able to distinguish between the OS terminating the process for resource reclamation vs GV terminating due to a clean shutdown (GV typically does not let the content process go through clean shutdown). I think we might need to add this probe at the GV level in order to make that distinction.

Comment 1

[(No longer employed by Mozilla) Aaron Klotz]

Nominating for 81 sprint.

Comment 2

[Amedyne Moya [:amoya]]

Lowering priority. We do not think this is needed now.

Comment 3

[(No longer employed by Mozilla) Aaron Klotz]

I'm not so sure we can do this within GV in such a way that it would be effective in Fenix. Given the way that AC handles sessions vis-á-vis content process kills, I think it is probably best handled there. I filed https://github.com/mozilla-mobile/android-components/issues/9366 for this.

Comment 4

[(No longer employed by Mozilla) Aaron Klotz]

Resolved via probes added to AC by Sebastian.

Comment 5

[Chris Peterson [:cpeterson]]

Moving content process management bugs to the new GeckoView::Sandboxing component.