Launcher Process: Add a SEH handler to PostCreationSetup
Categories
(Firefox :: Launcher Process, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox69 | --- | affected |
People
(Reporter: bugzilla, Unassigned)
References
Details
The idea here is that we can catch any exceptions and record them via our error handler.
Reporter | ||
Comment 1•5 years ago
|
||
I'm not sure that we actually want to do this, but I've filed it as food for thought. In particular, we'd have to run under the same restrictions as the crash reporter, and our error handler isn't really set up for that. We might just have to rely on WER.
Reporter | ||
Comment 2•5 years ago
|
||
Another idea here could be to use WER APIs to at least enhance any reports we get.
Eg. the launcher process could register the browser process via WerRegisterAdditionalProcess
In particular, we'd have to run under the same restrictions as the crash reporter
Out of curiosity, what restrictions did you have in mind?
Reporter | ||
Comment 4•5 years ago
|
||
(In reply to David Major [:dmajor] from comment #3)
In particular, we'd have to run under the same restrictions as the crash reporter
Out of curiosity, what restrictions did you have in mind?
Not being able to touch global state such as the memory allocator.
Reporter | ||
Comment 5•5 years ago
|
||
While we wouldn't be able to do a full launcher failure ping, I think we could do a DisableDueToFailure
, which is probably enough.
Reporter | ||
Updated•5 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•