TelemetrySession schedules some activities on idle, to avoid hogging resources.
Sometimes we're forced to handle these situations on a more rigid timeline than
"wait for idle". In those cases we should cancel the idle timeout so it doesn't
double-perform the operations.
Unfortunately idleDispatchToMainThread doesn't have a cancel mechanism, so we
need to bolt one over it.
MozReview-Commit-ID: JpUfb9rK2Od
With the removal of the old addonHistograms, all histograms are now registered.
So removing registered(Keyed)Histograms should be straightforward?
Unfortunately not, as this was how we filtered data based on dataset
(opt-in/opt-out), so a little more fiddling was needed to get C++ to only
serialize dataset-appropriate data (instead of post-facto filtering it in JS).
MozReview-Commit-ID: HDplhmzmzJl
This is the first part of purging the existing telemetry code for
ThreadHangStats from the tree. All of these features will be replaced with new
code for BHR telemetry in the future.
MozReview-Commit-ID: BhD5zY2LwUR
To cut down on complexity, we don't require specifying any expiry versions.
Given that these events will be recorded non-persistently from off-train add-ons, they can be expired by shipping new add-on releases.
We also start to use the new "record on release" terminology here instead of opt-in/opt-out, but are not changing the internal functionality yet.
Technically, this is implemented by keeping a separate registry for the dynamic event information.
Built-in & dynamic events are tracked with separate numeric ids, so introduce a common identifier for both, an EventKey.
For actual event storage, the events are treated the same as built-in events. They are simply bucketed into the 'dynamic' process storage.
This approach ends up duplicating code paths that use the event info, but keeps a single implementation for recording, storage & serialization.
TelemetrySession's getKeyedHistograms asks for each keyed histogram
individually. This is inefficient and doesn't work well with the storage
refactor.
So, plumb through a subsession keyed histogram snapshot API and convert
TelemetrySession over to using it.
MozReview-Commit-ID: Af9dTqw99UA
Previously we were doing bad string manipulation nonsense. Now when asked for
snapshots C++ can return a properly-formated Object tree.
MozReview-Commit-ID: HAvIbgzUvMU
TelemetrySession's getKeyedHistograms asks for each keyed histogram
individually. This is inefficient and doesn't work well with the storage
refactor.
So, plumb through a subsession keyed histogram snapshot API and convert
TelemetrySession over to using it.
MozReview-Commit-ID: Af9dTqw99UA
Previously we were doing bad string manipulation nonsense. Now when asked for
snapshots C++ can return a properly-formated Object tree.
MozReview-Commit-ID: HAvIbgzUvMU
This allows to move it out of the user's way, in case we need to gather
telemetry data to build a daily/aborted-session ping.
MozReview-Commit-ID: BrKZHKOJzqk
This defers the |gatherMemory| telemetry measurement until we're idle. This
measurement should no longer affect CC times.
MozReview-Commit-ID: DMtAo3K59FV
TelemetrySession.jsm gets "MEMORY_HEAP_ALLOCATED" by calling nsIMemoryReporter::GetHeapAllocatedAsync()
to get the attribute asynchronously using a callback.
MozReview-Commit-ID: 2PjOU68FanK
This allows to move it out of the user's way, in case we need to gather
telemetry data to build a daily/aborted-session ping.
MozReview-Commit-ID: BrKZHKOJzqk
GHOST_WINDOWS will be used to satisfy Quantum release criteria. As such, we
need release-channel collection.
Near as I can tell the memory manager works just as well in Release as in
pre-release, so this should be all that's necessary.
MozReview-Commit-ID: 1iLJhlgKoVQ
It schedules the ping to be sent on new profiles after 30 minutes
from the Firefox startup. The ping is eventually sent at shutdown
if the scheduled time wasn't reached.
To reliably prevent sending the ping more than once, the "session-state.json"
file is used to keep track of the "sent" state.
The "new-profile" ping is protected behind a pref, disabled by default
in this patch.
MozReview-Commit-ID: 4g4lPRXe9q6
addonHistograms isn't being used and has started getting in the way.
So it goes.
Leave the "Addon Histograms" section in about:telemetry for 60 days.
Remove it in bug 1355882
MozReview-Commit-ID: 4lm7ONirofl
