Closed Bug 533234 Opened 15 years ago Closed 8 years ago

Record when startup is complete

Categories

(Toolkit :: Crash Reporting, defect)

Product:
Toolkit
Component:
Crash Reporting
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1295934

People

(Reporter: sicking, Unassigned)

References

Details

See bug 531870 comment 9. Over in bug 531870 we're trying to figure out why we're sometimes lacking extension information. One known reason for lacking extension information is due to crash during startup. So it might help with bug 531870 if we recorded when startup had succeeded successfully. (of course, even better would be if we could record the list of addons even if we crash during startup.)
Blocks: 531870
OS: Mac OS X → All
Hardware: x86 → All
From that comment "we could add another annotation, like Startup=1 immediately at app startup, and then set it to Startup=0 from the browser chrome onload, as a rough gauge of "crashed in startup"". I don't know if that's exactly right, but it'd probably serve.
For telemetry, we started recording a flag about the state the process is in, including "startup", and we probably should include exactly that flag. This would also enable us to get more detail, or even have a "shutdown" state and similar tings reported in that field. The focus is startup right now, but others might make sense as well.
Blocks: 524568
From the discussion today, interesting crash annotations in this area would be: startup, shutdown; restart-on-crash, other kinds of restart
Bug 1295934 added a "StartupCrash" annotation.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.