I ran the backfill branch on yesterday's nightly pings and some of the new fields are all null: histogram_content_memory_distribution_among_content histogram_content_memory_heap_committed_unused histogram_content_memory_total histogram_content_memory_unique histogram_gpu_memory_distribution_among_content histogram_gpu_memory_heap_allocated histogram_gpu_memory_heap_committed_unused histogram_gpu_memory_resident_fast histogram_gpu_memory_total histogram_gpu_memory_unique histogram_gpu_memory_vsize histogram_gpu_memory_vsize_max_contiguous histogram_parent_memory_heap_committed_unused Can you verify the names and whether we should be seeing data in these histograms? If these are just that rare or not being recorded properly, I vote we remove them as columns for the backfill and file bugs for the owners if warranted.
These have been automatically added through the `MainPing.histogramsToRow` function. It looks like the gpu rows should not be there and may be a bug with com.mozilla.telemetry.metrics.Histogram. The content fields look like they have mistakenly been specified to be overly broad. For example, MEMORY_TOTAL is specified for the parent and content process  but is only recorded in the parent process .  https://dxr.mozilla.org/mozilla-central/source/toolkit/components/telemetry/Histograms.json#1338  https://dxr.mozilla.org/mozilla-central/rev/580d833df9c44acec686a9fb88b5f27e9d29f68d/toolkit/components/telemetry/TelemetrySession.jsm#1130-1162
Bugs were filed to remove the excess histogram values. See bug 1442441, 1442402, and 1442061.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.