Bug 41565: Gate Telemetry Tasks behind MOZ_TELEMETRY_REPORTING

Merge Info

• Related Issues

  • #41565 (closed)

• Backport Timeline

  • Immediate - patchsets for critical bug fixes or other major blocker (e.g. fixes for a 0-day exploit) OR patchsets with trivial changes which do not need testing (e.g. fixes for typos or fixes easily verified in a local developer build)
  • Next Minor Stable Release - patchset that needs to be verified in nightly before backport
  • Eventually - patchset that needs to be verified in alpha before backport
  • No Backport - patchset for the next major stable

• Upstream Merging

  • Merge to base-browser - typically for !fixups to patches in the base-browser branch, though sometimes new patches as well
    • NOTE: if your changeset includes patches to both base-browser and tor-browser please please make separate merge requests for each part

• Issue Tracking

  • Link resolved issues with appropriate Release Prep issue for changelog generation

Change Description

Fixes #41565 (closed). The motivation here is to avoid the disk activity and performance impact of telemetry tasks if MOZ_TELEMETRY_REPORTING was not defined. Some testing may be needed to ensure the changes are optimal and do not cause any issues.

The patch for nsAppRunner.cpp wasn't tested and needs to be verified. It should disable the task that creates Telemetry.FailedProfileLocks.txt in the profile folder. It can be tested by launching the browser process while the browser is already open.

Files and preferences that will be disabled by these changes:

(BrowserUsageTelemetry.reportProfileCount) (Windows only)
Browser\profile_count_UpdateInfo.json

(TelemetryEnvironment.jsm)
profile.default\times.json

(browser.js)
fission.experiment.max-origins.last-disqualified
fission.experiment.max-origins.last-qualified
fission.experiment.max-origins.qualified

(this._collectStartupConditionsTelemetry)
browser.startup.lastColdStartupCheck