Add command line argument to allow overriding of default crash reporter behavior
Categories
(Testing :: geckodriver, task, P3)
Tracking
(firefox124 fixed)
Tracking | Status | |
---|---|---|
firefox124 | --- | fixed |
People
(Reporter: whimboo, Assigned: rzvncj, Mentored)
References
Details
(Whiteboard: [lang=rust])
Attachments
(1 file)
By default geckodriver turns off the crash reporter so it doesn't interfere with application shutdown. This is done by setting the following environment variables:
- MOZ_CRASHREPORTER="1"
- MOZ_CRASHREPORTER_NO_REPORT="1"
- MOZ_CRASHREPORTER_SHUTDOWN="1"
Given that in some cases users aren't able to retrieve the crash report it would be good to have a command line argument that disables setting these env variables for both desktop and mobile. Then it can be used to investigate crash scenarios related to Firefox.
My proposal would be an argument like --enable-crash-reporter
.
Reporter | ||
Updated•1 year ago
|
Reporter | ||
Comment 1•1 year ago
|
||
Hello Razvan, given your interest in contributing Rust code and as well learning more about this language I think that this bug should be a good one for you. It would also help some of our users to actually send crash reports in cases when they cannot fetch the minidump files on their own. Let me know if you have interest. Thanks.
Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Reporter | ||
Comment 3•1 year ago
|
||
Hi Gabriele, please note that we want to add an option for geckodriver users to enable the crash reporter in situations when automation cannot easily export the minidump files. I wonder if we should maybe add a Remote Protocol
tag or similar to the .extra file to let crash-stats know that this report is coming from automation. What do you think? Thanks!
Updated•1 year ago
|
Comment 5•1 year ago
|
||
bugherder |
Reporter | ||
Comment 6•1 year ago
|
||
Razvan, thanks a lot for this new feature which we will ship with 0.35.0. Lets see if it will be already helpful for https://github.com/mozilla/geckodriver/issues/2153 to identify the crash details.
If you are interested in another bug to work on and you cannot find one just let me know.
Assignee | ||
Comment 7•1 year ago
|
||
Happy to help! I've taken a shot at bug 1877649 also.
Feel free to add me to the CC of any bug you think I might be able to help with, and I'll receive an email notice and do my best to help if I can. Thanks!
Comment 8•1 year ago
|
||
(In reply to Henrik Skupin [:whimboo][⌚️UTC+1] from comment #3)
Hi Gabriele, please note that we want to add an option for geckodriver users to enable the crash reporter in situations when automation cannot easily export the minidump files. I wonder if we should maybe add a
Remote Protocol
tag or similar to the .extra file to let crash-stats know that this report is coming from automation. What do you think? Thanks!
I think that's a very good idea. We already have something similar for how the crash was submitted (see the SubmittedFrom crash annotation). You can either add to that if automation submits the crash reports on its own or add a new annotation specifically to say that it was generated in automation (but submitted using one of the existing mechanisms).
Reporter | ||
Comment 9•1 year ago
|
||
Thanks. I filed bug 1880257 as a follow-up for the crash annotation.
Description
•