-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash reports contain guid and env #8865
Crash reports contain guid and env #8865
Comments
Looks like this was never tested @bridiver because the milestone is missing. This was merged into 1.8 - did you want to give things a look in Backtrace? I'll go ahead and posthumously assign the 1.8 milestone to this and remove |
Found this was not working as expected during troubleshooting session with @NejcZdovc @bridiver suggested a patch which I just verified |
Verification PASSED on
Reproduced the original issue using
Examples: Being sent via Not being sent via Verification passed on
Unable to check on Linux due to known issue #4296 Attempted using
|
@bsclifton @bridiver is there a way to see if the |
@kjozwiak yup- above looks perfect! 😄👌 I don't think |
Description
Crash reports contain a guid and env info
Steps to Reproduce
brave://crash
brave://crashes
and ensure the crash has been sentActual result:
unique guid is present
env vars are also stripped by backtrace so this can't be verified directly through the UI, but we are definitely sending them
Expected result:
guid should be 0 or not present
Reproduces how often:
always
Brave version (brave://version info)
yes
yes
yes
yes
The text was updated successfully, but these errors were encountered: