1355611 - Don't load TelemetryStartup.js in the content process

Status: RESOLVED FIXED

(Toolkit :: Telemetry, defect, P2)

Description

[Andrew McCreight [:mccr8]]

TelemetryStartup.js is an XPCOM component. It gets loaded in every parent and content process, and persists through the lifetime of the process. What it seems to do is listen for profile-after-change (in the parent) or app-startup (in content processes) and runs some code. Maybe this could be turned into a script loaded from MainProcessSingleton.js and ContentProcessSingleton.js.

Comment 1

[Andrew McCreight [:mccr8]]

The code that TelemetryStartup runs in the content process is really simple, and that's what I care more about anyways (due to the increasing number of content processes) so I'll just fix that here.

Comment 2

[Andrew McCreight [:mccr8]]

Attachment: Bug 1355611 - Don't load TelemetryStartup.js in the content process.

Instead, run the telemetry startup in ContentProcessSingleton.js, to
avoid loading a .jsm in every content process.

Review commit: https://reviewboard.mozilla.org/r/129486/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/129486/

Comment 3

[Georg Fritzsche [:gfritzsche]]

Comment on attachment 8857517 [details]
Bug 1355611 - Don't load TelemetryStartup.js in the content process.

https://reviewboard.mozilla.org/r/129486/#review132042

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/3971646449ae
Don't load TelemetryStartup.js in the content process. r=gfritzsche

Comment 5

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

https://hg.mozilla.org/mozilla-central/rev/3971646449ae