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
chore: add V8 crash information to crashReporter #24771
Conversation
a860b83
to
bc89ff5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fantastic stuff 🥳
bc89ff5
to
1569643
Compare
1569643
to
c0a3138
Compare
Release Notes Persisted
|
I was unable to backport this PR to "10-x-y" cleanly; |
I was unable to backport this PR to "9-x-y" cleanly; |
@codebytere has manually backported this PR to "9-x-y", please check out #24864 |
@codebytere has manually backported this PR to "10-x-y", please check out #24866 |
volatile int* zero = nullptr; | ||
*zero = 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, why introduce new crash code rather than calling ElectronBindings::Crash()?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description of Change
This PR restores our use of a custom V8 fatal error handler with the purpose of improving crash reports for crashes originating in V8. When a v8 crash occurs, the message and location will be added as extra parameters to the crash report for more effective debugging.
cc @MarshallOfSound
Checklist
npm test
passesRelease Notes
Notes: Added V8 crash message and location information to crashReport parameters.