I believe [this](https://crash-stats.mozilla.org/report/index/564f3ae8-ecf5-488b-b8c7-e73050240320) is the relevant the crash report. n.b. `default-browser-agent.exe` is a thin wrapper that calls `firefox.exe --backgroundtask defaultagent ...`. In this case it does some other logic in `default-browser-agent.exe` but we would not expect the relevant logic to hang, whereas we have an existing crash report that matches the description for the Firefox background task that would have also run at this time. :mhughes we might consider dropping to P3 S3. This doesn't impact many users - there's been no spike in crash reports and it's not immediately reproducible.
Bug 1886524 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I believe [this](https://crash-stats.mozilla.org/report/index/564f3ae8-ecf5-488b-b8c7-e73050240320) is the relevant the crash report. n.b. `default-browser-agent.exe` is a thin wrapper that calls `firefox.exe --backgroundtask defaultagent ...`. In this case it does some other logic in `default-browser-agent.exe` but we would not expect the relevant logic to hang, whereas we have an existing crash report that matches the description for the Firefox background task that would have also run at this time. __Edit:__ The linked crash report would only be tangentially related if at all, as the relevant XPCOM object is not used when registering the scheduled task. Curiously though the background task was run immediately after installation and seemingly timed out? :mhughes we might consider dropping to P3 S3. This doesn't impact many users - there's been no spike in crash reports and it's not immediately reproducible.
I believe [this](https://crash-stats.mozilla.org/report/index/564f3ae8-ecf5-488b-b8c7-e73050240320) is the relevant the crash report. n.b. `default-browser-agent.exe` is a thin wrapper that calls `firefox.exe --backgroundtask defaultagent ...`. In this case it does some other logic in `default-browser-agent.exe` but we would not expect the relevant logic to hang, whereas we have an existing crash report that matches the description for the Firefox background task that would have also run at this time. __Edit:__ The linked crash report would only be tangentially related if at all, as the relevant XPCOM object is not used when registering the scheduled task. Curiously though the background task was run immediately after installation and seemingly timed out (so maybe still related)? :mhughes we might consider dropping to P3 S3. This doesn't impact many users - there's been no spike in crash reports and it's not immediately reproducible.