Closed
Bug 1210658
Opened 9 years ago
Closed 9 years ago
Need exception handling in assemblePayloadWithMeasurements
Categories
(Toolkit :: Telemetry, defect, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
mozilla44
Tracking | Status | |
---|---|---|
firefox44 | --- | fixed |
People
(Reporter: vladan, Assigned: gfritzsche)
References
(Blocks 1 open bug)
Details
(Whiteboard: [unifiedTelemetry] [measurement:client])
Attachments
(2 files)
4.25 KB,
patch
|
Dexter
:
review+
|
Details | Diff | Splinter Review |
1.83 KB,
patch
|
Dexter
:
review+
|
Details | Diff | Splinter Review |
TelemetrySession.jsm calls into native code using XPIDL but the C++ implementations of those XPIDL interfaces sometimes return nsresult failure codes. An nsresult error rturn will trigger a JS exception in the calling code and TelemetrySession.jsm isn't set up to recover from such exceptions. Calling code (no exception handler): http://hg.mozilla.org/mozilla-central/annotate/2c1fb007137d/toolkit/components/telemetry/TelemetrySession.jsm#l1266 Native, exception-throwing code (only one example): http://mxr.mozilla.org/mozilla-central/source/toolkit/components/telemetry/Telemetry.cpp#3555
Assignee | ||
Comment 1•9 years ago
|
||
Also chromeHangs, threadHangStats, etc.: http://hg.mozilla.org/mozilla-central/annotate/2c1fb007137d/toolkit/components/telemetry/TelemetrySession.jsm#l1254 I think in general we need an in-depth review of exception-safety of the Telemetry modules, but this seems like a path we should fix soon.
Updated•9 years ago
|
Points: --- → 1
Priority: P3 → P1
Updated•9 years ago
|
Priority: P1 → P2
Assignee | ||
Updated•9 years ago
|
Priority: P2 → P1
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → gfritzsche
Assignee | ||
Updated•9 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•9 years ago
|
||
This is specifically addressing the ping assembly code path. Further exception handling review will happen in bug 1177958 or other separate follow-ups.
Attachment #8675687 -
Flags: review?(alessio.placitelli)
Assignee | ||
Comment 3•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=e2a512af0022
Comment 4•9 years ago
|
||
Comment on attachment 8675687 [details] [diff] [review] Protect Telemetry ping assembly from exceptions in data gathering functions Review of attachment 8675687 [details] [diff] [review]: ----------------------------------------------------------------- This looks good. Should we mention in the docs (i.e. main-ping.rst) that sections of the payload can be null due to client errors?
Attachment #8675687 -
Flags: review?(alessio.placitelli) → review+
Assignee | ||
Comment 5•9 years ago
|
||
Attachment #8675751 -
Flags: review?(alessio.placitelli)
Updated•9 years ago
|
Attachment #8675751 -
Flags: review?(alessio.placitelli) → review+
https://hg.mozilla.org/integration/fx-team/rev/28a844f6cd11 https://hg.mozilla.org/integration/fx-team/rev/9a1f6c87afc8
Comment 7•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/28a844f6cd11 https://hg.mozilla.org/mozilla-central/rev/9a1f6c87afc8
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox44:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla44
Comment 8•9 years ago
|
||
This code here actually introduce a new bug: https://dxr.mozilla.org/mozilla-central/source/toolkit/components/telemetry/TelemetrySession.jsm#1246 this.log is undefined in that line. I'm guessing this._log was the intention. Should I re-open this bug here, or if you agree on using this._log instead should I simply land the fix together with my code in bug 1198883?
Flags: needinfo?(gfritzsche)
Comment 9•9 years ago
|
||
Reopening until the problem in comment #8 has been resolved. Bug fix for it can be found in bug 1198883.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 10•9 years ago
|
||
Ah, thanks for the find. This bug was merged to mozilla-central, any follow-up work should be in other bugs. I'll open one and flag you there.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Flags: needinfo?(gfritzsche)
Resolution: --- → FIXED
Assignee | ||
Comment 11•9 years ago
|
||
(In reply to Georg Fritzsche [:gfritzsche] from comment #10) > Ah, thanks for the find. > This bug was merged to mozilla-central, any follow-up work should be in > other bugs. > I'll open one and flag you there. Looking in your bug, this seems easy to handle there, lets just do that.
You need to log in
before you can comment on or make changes to this bug.
Description
•