Closed
Bug 1621177
Opened 5 years ago
Closed 3 years ago
Two errors are recorded in the EventLog if -log-launcher-error is used
Categories
(Firefox :: Launcher Process, defect, P3)
Tracking
()
RESOLVED
FIXED
99 Branch
| Tracking | Status | |
|---|---|---|
| firefox99 | --- | fixed |
People
(Reporter: toshi, Assigned: rkraesig, Mentored)
Details
Attachments
(1 file)
This is a trivial issue. If we launch firefox.exe with the -log-launcher-error option, we record the same error twice because PostErrorToLog is called in the main thread and the thread which sends a ping.
Comment 1•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)
Severity: normal → S3
| Reporter | ||
Updated•5 years ago
|
Severity: S3 → S4
Updated•4 years ago
|
Assignee: nobody → rkraesig
Updated•4 years ago
|
Mentor: tkikuchi
| Assignee | ||
Comment 2•3 years ago
•
|
||
Post a launcher error to the Event Log only after an attempt to send it
via telemetry has concluded, whether in success or in failure.
This implies that the thread which posts the log is:
- in the failure case, whichever thread learns about the failure;
- in the success case, the ping thread, because only it learns about
success.
(Additionally, check for -- and log -- failure of _beginthreadex.)
Pushed by rkraesig@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/46ebc949c3af
post error to Event Log only after telemetry attempt r=tkikuchi
Comment 4•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox99:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•