Bugzilla

We need to measure impact of DevTools sessions across over time.

The assumptions are:

1) Leaks occur during general usage but especially page refreshes and live reloading.
2) Some leaks are limited to the toolbox lifespan and collected after closing; while some leaked data are not collected
3) Some recent leaks have been identified on the content process, while we also know about frontend leaks on the parent process.

The best case would be to collect memory size on both parent and content process. We could take memory snapshots 1) after opening DevTools 2) before closing DevTools and 3) after closing and GC. An MVP could report just the memory diff from 2) to 3).

Since memory measurements can be expensive for performance; we probably want to limit collection to Nightly and DevEdition.

One open question would be if we want to force GC to get accurate measurements after closing DevTools.

We need to measure impact of DevTools sessions across over time.

The assumptions are:

1) Leaks occur during general usage but especially page refreshes and live reloading.
2) Some leaks are limited to the toolbox lifespan and collected after closing; while some leaked data are not collected
3) Some recent leaks have been identified on the content process, while we also know about frontend leaks on the parent process.

The best case would be to collect memory size on both parent and content process. Related, the current `memory_total` probe is only collected for parent process: https://probes.telemetry.mozilla.org/?search=memory_total&view=detail&probeId=histogram%2FMEMORY_TOTAL

We could take memory snapshots 1) after opening DevTools 2) before closing DevTools and 3) after closing and GC. An MVP could report just the memory diff from 2) to 3).

Since memory measurements can be expensive for performance; we probably want to limit collection to Nightly and DevEdition.

One open question would be if we want to force GC to get accurate measurements after closing DevTools.