Consider adding telemetry for failures in startup/per-window tasks through callModulesFromCategory
Categories
(Firefox :: General, task)
Tracking
()
People
(Reporter: Gijs, Unassigned)
References
(Blocks 1 open bug)
Details
One of the benefits of callModulesFromCategory is that it makes it easy to collect error (failure) information in a single place.
Historically we've had issues where "something breaks" on startup and that then wrecks the browser. In fact, those issues aren't entirely historical yet, cf. bug 1955803. But it's difficult to work out what portion of startup caused initialization to fail and why, and we depend on bug reports and reporters willing to do some digging to figure this out.
If we had telemetry on which components broke during startup or window opening, that would allow us to spot spikes/problems sooner, and hopefully that would then allow us to fix them before we get to release.
Updated•8 months ago
|
Comment 1•5 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox Build System::Task Configuration' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•5 months ago
|
||
The bot is wrong.
Description
•