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
fix: crash reporting on Windows on Arm #19391
fix: crash reporting on Windows on Arm #19391
Conversation
linux-arm64-testing seems to have failed due to a corrupt sscache stream (should be unrelated to the change). |
d0a57a4
to
0b62702
Compare
I've reconfigured this PR to only apply these two patches when targetting arm64. @jkleinsc can you update our CI to set the |
WOA build with latest commits here: https://ci.appveyor.com/project/electron-bot/electron-ldhmv/builds/26428202 |
CI flaked with this (unrelated) test
@jkleinsc: could you kick off a build for Windows on Arm? |
NB @jkleinsc: there should be two additional patches applied after the rest of them. Is |
The |
The |
So, if everything's building right, together with #19366 and the optional #19383, we should get a test run like the following (i.e. about 2-4 unit test failures). electron-6-0-x-integration-output.log One other thing that occurred to me is that because dugite doesn't know how to install git prebuilts on Windows on Arm, you have to install the x86 version of Git onto the test machine and set |
@richard-townsend-arm can you rebase this with the latest from 6-0-x? I just merged in the changes so that we can properly build WOA. |
Rebasing now... |
This commit backports [1] (originally written by @ThomsonTan) into V8 7.6. With this patch in place, calls made from JS into the atom core which crash electron.exe will now generate crash dumps on Windows on Arm rather than silently dying. [1] https://chromium-review.googlesource.com/c/v8/v8/+/1701133/11
Backport of [1] (originally written by @kaadam) to Chromium 76's crashpad. This lets you see the register values within the crash dump. [1] https://chromium-review.googlesource.com/c/crashpad/crashpad/+/1632749
3605ce3
to
3a1b8e7
Compare
Cool, so I've confirmed that it builds for WoA, unsure whether it works yet because all my WoA devices are offline, I'm OoO and unable to go kick them. |
win-ia32-testing-pr has flaked due to an unrelated issue:
|
WOA build running here: https://ci.appveyor.com/project/electron-bot/electron-ldhmv/builds/26965410 |
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.
LGTM
Release Notes Persisted
|
Description of Change
This PR contains two back-ports from Chromium 77:
Together, these allow electron to generate crash reports in all circumstances. Previously, if native C++ code (in, say, atom or a node module) was called from Javascript and a fatal exception occurred (e.g. a null pointer dereference), Windows would not be able to unwind the stack correctly and find an exception handler. It would then kill the electron process without leaving behind any indication of what caused the crash. This V8 change, alongside the crashpad capture context changes, mean that field crash reports can be collected for Windows on Arm applications.
CC: @jkleinsc
Checklist
npm test
passesRelease Notes
Notes: no-notes