Use minidump-analyzer to append Windows AV/spyware/firewall data to crashreport .extra file; add to telemetry environment data lazily
Categories
(Toolkit :: Crash Reporting, task)
Tracking
()
People
(Reporter: Gijs, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: main-thread-io, perf, perf:startup, Whiteboard: [fxperfsize:S])
Per discussion in bug 1363586, once we switch the .extra file to be nicer, we can move the AV/firewall/spyware data into the minidump-analyzer code, instead of trying to do the (windows-API-based) IO early on startup.
For telemetry, we can do the same stuff on an idle task later, OMT, after startup, and update the environment then.
|
Reporter | |
Updated•6 years ago
|
|
|
Reporter | |
Comment 1•3 years ago
|
||
Gabriele: blast from the past! Do you know if this report is still current? Is the extra file nicer now? ;-)
|
|
Reporter | |
Updated•3 years ago
|
|
||
Comment 2•3 years ago
|
||
Yes, the .extra file is JSON since bug 1420363, adding structured stuff to it should be much easier.
|
||
Updated•3 years ago
|
|
|
Reporter | |
Comment 3•5 months ago
|
||
I don't suppose you have an example of a small addition to these annotations that could be used to figure out how to do this? Then I might be able to find time to (finally!) actually do this part. :-)
|
|
||
Comment 4•4 months ago
|
||
I have! If this information can be retrieved from outside of Firefox then you can do it in the minidump analyzer like we do for the DLL signatures. See the code here that sets the ModuleSignatureInfo crash annotation and the implementation here. We have to call a bunch of Windows function for that and we put them here.
Description
•