electron
electron copied to clipboard
[Bug]: App crashes during startup in IntentionallyCrashBrowserForUnusableGpuProcess()
Preflight Checklist
- [X] I have read the Contributing Guidelines for this project.
- [X] I agree to follow the Code of Conduct that this project adheres to.
- [X] I have searched the issue tracker for a bug report that matches the one I want to file, without success.
Electron Version
28.3.3
What operating system(s) are you using?
Windows
Operating System Version
win11 22631.3880
What arch are you using?
x64
Last Known Working Electron version
28.3.3
Expected Behavior
The application starts normally
Actual Behavior
Application startup crashes
Testcase Gist URL
No response
Additional Information
Processor: AMD Ryzen 5 5500U with Radeon Graphics2.10 GHZ
This is the error log generated by CrashDumps
Microsoft (R) Windows Debugger Version 10.0.22621.3233 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\catch\Property(2)\crashDumps\reports\f3c2654c-2334-4ee4-9a66-d5d2e0a1ed19.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Version 22631 (3880) MP (12 procs) Free x64
Product: WinNt
Edition build lab: Windows NT 10.0.22631.3880
Machine Name:
Debug session time: Wed Jul 31 17:37:51.000 2024 (UTC + 8:00)
System Uptime: not available
Process Uptime: 0 days 0:00:02.000
................................................................
..............
Loading unloaded module list
.
This dump file has a breakpoint exception stored in it.
The stored exception information can be accessed via .ecxr.
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify checksum for ntdll.dll
ntdll!NtDelayExecution+0x14:
00007ffc`27e50624 c3 ret
Hello @remloyal. Thanks for reporting this and helping to make Electron better!
The version of Electron reported in this issue has reached end-of-life and is no longer supported. If you're still experiencing this issue on a supported version of Electron, please update this issue to reflect that version of Electron.
Now adding the https://github.com/electron/electron/labels/blocked%2Fneed-info%20%E2%9D%8C label for this reason. This issue will be closed in 10 days if the above is not addressed.
It seems the dump file is mini dump, and you should set program executable file search path and symbol search path in the WinDbg, and try analyzing the dump file again.
This is the complete parsing log, represented by symbol.
Can anyone help me? thank you
This is a new log that can run normally on some computers, but not on others
1 Demo.exe!static void content::`anonymous namespace'::IntentionallyCrashBrowserForUnusableGpuProcess()
That sounds relevant :slightly_smiling_face:
CC #35180, #38284 that have a similar crash message
1 Demo.exe!static void content::`anonymous namespace'::IntentionallyCrashBrowserForUnusableGpuProcess()
That sounds relevant 🙂
CC #35180, #38284 that have a similar crash message
But when I disable GPU: app.disableHardwareAcceleration() and app.disableDomainBlockingFor3DAPIs() It still cannot run normally. Is it related to IntentionallyCrashBrowserForUnusableGpuProcess?
could you please launch the APP in the terminal with appended command --enable-logging=stderr and collect the log?
1 Demo.exe!static void content::`anonymous namespace'::IntentionallyCrashBrowserForUnusableGpuProcess()
That sounds relevant 🙂
CC #35180, #38284 that have a similar crash message
Hello, after testing and verification, it is good in the C drive directory, but other drives will crash
The tested and verified versions include 28, 29, and 31, all of which will report the same error
#38284
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue.