Bugzilla

Thanks, Steve, for looking into this and the summary!

> Who could do the Android-side plumbing?

The Android team can work on / help with this if we all agree that it's worth doing. Based on your summary, I agree that (c) would be worth trying.

> Also, based on skimming through Android docs, it seems like it would be useful to have profiler markers for lifecycle callbacks: onStop, onPause, onResume, etc. 

Yes, we can add those. We currently only have a marker for `onStart`. I filed bug 1811133 for this.

>  I should also mention that at least for this specific profile, fixing GC probably wouldn't prevent it from being killed. That would require slowing down setTimeout callbacks or something.

Yes, I think that's right for this particular page. The GC work would also affect otherwise "well-behaved" sites though, IIUC. Of course, it would be worse for pages with lots of work triggered by timeouts. Throttling timouts seems to already be supported though, and I wonder if we could "simply" configure this more aggressively on Android? Andreas, I found your old post about this [1] and bug 1377766. Does that sound reasonable / doable to you?

[1] https://groups.google.com/g/mozilla.dev.platform/c/hcEqovQrBts

Thanks, Steve, for looking into this and the summary!

> Who could do the Android-side plumbing?

The Android team can work on / help with this if we all agree that it's worth doing. Based on your summary, I agree that (c) would be worth trying.

> Also, based on skimming through Android docs, it seems like it would be useful to have profiler markers for lifecycle callbacks: onStop, onPause, onResume, etc. 

Yes, we can add those. We currently only have a marker for `onStart`. I filed bug 1811133 for this.

>  I should also mention that at least for this specific profile, fixing GC probably wouldn't prevent it from being killed. That would require slowing down setTimeout callbacks or something.

Yes, I think that's right for this particular page. The GC work would also affect otherwise "well-behaved" sites though, IIUC. Of course, it would be worse for pages with lots of work triggered by timeouts. Throttling timouts seems to already be supported though, and I wonder if we could "simply" configure this more aggressively on Android? Andreas, I found your old post about this [1] and bug 1377766. Does that sound reasonable to you? I am also wondering if this functionality is active / working correctly on Android, since the timeouts seem not affected in the profile above.

[1] https://groups.google.com/g/mozilla.dev.platform/c/hcEqovQrBts