Use Necko as the primary means to submit pings/reports from the crash reporter
Categories
(Toolkit :: Crash Reporting, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox141 | --- | fixed |
People
(Reporter: afranchuk, Assigned: afranchuk)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
In https://docs.google.com/document/d/1hpiiywAWDXoPlXHQNPmduyjFTbK_sEFRc8JXV60_n3A we discussed the interaction of the crash reporter and the pingsender, and how networking should work in the future. We decided that the crash reporter should use Necko as the primary means of sending pings/reports, with a fallback using system network stacks (through curl/libcurl, which are available on all target platforms).
The crash reporter is currently using the fallback network stacks as the sole means of sending reports, and is using pingsender (which uses system network stacks itself) for pings.
Using Necko is convenient as it will take into account user settings, such as proxy configurations, and also relies minimally on the system environment. Having a fallback is important if whatever causes Firefox to crash also causes background tasks using Necko to crash.
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Backed out for causing build bustages @ust.mk.
Comment 8•11 months ago
|
||
Backed out for causing build bustages
- Backout link
- Push with failures
- Failure Log
- Failure line: error: test failed, to rerun pass
-p crashreporter --bin crashreporter
Comment 10•11 months ago
|
||
Comment 11•11 months ago
|
||
| bugherder | ||
Updated•10 months ago
|
Updated•10 months ago
|
Description
•