Closed PassionPenguin closed 3 years ago
Thanks for reporting this and helping to make Electron better!
Because of time constraints, triaging code with third-party dependencies is usually not feasible for a small team like Electron's.
Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.
Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.
I'm adding the blocked/need-repro
label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.
how can electron fiddle trigger a system fatal crash and make a forced restart?
Preflight Checklist
Electron Version
13.2.1
What operating system are you using?
macOS
Operating System Version
Darwin Penguins-MBP 20.5.0 Darwin Kernel Version 20.5.0: Sat May 8 05:10:33 PDT 2021; root:xnu-7195.121.3~9/RELEASE_X86_64 x86_64
What arch are you using?
x64
Last Known Working Electron version
13.2.1
Expected Behavior
Application run properly
(no code has changed before the session had started, just a simple restart)
Actual Behavior
a fatal crash, lead to black screen and a fatal crash in system (CPU 2 unresponsive, tlb flush timeout)
Testcase Gist URL
No response
Additional Information
Electron information
System Diagnostics
code ADP000 No issues found
macOS Output Log: