Drop in default agent telemetry after Default Agent background task migration
Categories
(Toolkit :: Default Browser Agent, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox120 | --- | affected |
People
(Reporter: nrishel, Assigned: nrishel)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidedi])
Attachments
(2 files)
There was a drop in telemetry after migrating the Default Agent to Firefox Background Tasks, seen in both Nightly and Beta builds.
Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Depends on D190636
Comment 4•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/39145ab8550f
https://hg.mozilla.org/mozilla-central/rev/db70bbc48ef5
Assignee | ||
Comment 5•1 year ago
•
|
||
We believe the issue remains as we're able to reproduce applications launched from the background task being closed with the background task. This could explain why our telemetry isn't sending, if pingsender
closes with the background task then telemetry would race shutdown.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
-backgroundtask
switch will set LauncherFlags::eWaitForBrowser
:
https://searchfox.org/mozilla-central/rev/7d77ff808f8407a3e4fc0911779da446c050f9ee/browser/app/winlauncher/LauncherProcessWin.cpp#153,161
if LauncherFlags::eWaitForBrowser
is set, the launcher process will create a job object and assign the browser process to the job object. So when the background task exits, all processes in the job object will be killed:
https://searchfox.org/mozilla-central/rev/7d77ff808f8407a3e4fc0911779da446c050f9ee/browser/app/winlauncher/LauncherProcessWin.cpp#486-487
We will have to break away from the job when executing pingsender
and the browser from Default Agent Notification.
Comment 7•1 year ago
|
||
Comment 8•1 year ago
|
||
Please also fix this comment because we need JOB_OBJECT_LIMIT_BREAKAWAY_OK
for a different reason.
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Description
•