-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
[Bug]: App launch failed with error- "gpu process launch failed: error_code=40" #32074
Comments
I have the same problem as you,It works with |
Please attach a crash dump. You can collect them by adding the following snippet to your main process code, before app.whenReady: const { app, crashReporter } = require('electron')
console.log(app.getPath('crashDumps'))
crashReporter.start({ submitURL: '', uploadToServer: false }) Then reproduce the crash, zip up the crash dumps directory and attach it here. |
Not changes after attaching your snippet code, kindly provide simple source code so that we can overcome from this issue. Best Regards |
@RohitRawat12 my snippet shows you how to collect a crash dump. If you supply the crash dump, I may be able to help further. |
Crashpad.zip |
A handful of our customers (all on Win10) report the same problem, the logs look like the following:
Just to put this out there, invisible windows work fine, so they start and load their HTML/JS correctly, however visible windows (such as most application's main window) gets created correctly but then crashes as soon as you try to load the HTML file. We upgraded our project from a really old Electron version (8.2.5), so the last working version of ours might not be useful, however I can report that this problem occurs in both, 16.0.7 as well as the latest 17.0.0 (which those logs were generated with). I'll try to verify if the |
Update: The Please find all the crashdumps attached, they are from three different users and each of them provided crashdumps with and without the sandbox flag (if that makes any difference in the dumps at all). I hope this issue can be solved quickly since I didn't find any more workarounds we could try. |
I was able to get my hands on two more crashdumps. Please find a zip with all the crashdumps (original three and the two new ones) attached. |
Hi, just started to use electron and it looks like I'm getting into same problem. I'm able to run app with |
And again new crashdumps from two more of our users. |
Update: After I stumbled upon many more command switches concerning the GPU in another open Electron bug (#30966), after I added all the ones below, it did actually render again for our users.
I'm not sure which specific one does the trick, however as stated previously, just adding the Hope that info helps a little, in conjunction with the crash reports. |
I found that the problem was not hardware, I reinstalled a clean version of the OS(Windows 10 pro 19041) from a running computer. It reappeared problem |
Bump: Has there been any progress on evaluating this particular problem and the crashreports? |
@nornagon any progress ? or any more specify information we need to collect from our client ? |
Ran into this issue when trying to run in a windows 11 vm on m1 mac running in parallels with both x64 and arm64 electron builds from electron-packager. Adding
I think Edit strike that, only using disable-gpu-sandbox makes it so the dev tools cannot be opened in any way. You need to use |
Any update are their? |
I ran into this issue when experimenting with16.2.8 and BoxedApp Packer (to make it a portable, single EXE on Windows). The "no-sandbox" CLI flag also resolved it in that case as well. FWIW, packaging to a "portable" app with electron-builder instead didn't have the issue in my tests, but I haven't yet tested the portable in an actual VM to see if it has the problem. |
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! |
Still an issue - I'm new to electron, but the initial setup you get when running I'm on Windows 11 with WSL |
have the same err in windows11 |
I have a similar error in Arch Linux kernel version 6.4.7-arch1-1:
Where are these error codes defined? This may give clues on what's going on. |
I experienced a similar error when the executable is placed on a network folder (a UNC path). in my case I am pretty sure that the error is related to chromium |
Yes, this is still an issue and I found that it is caused by running from a (mapped) network share. When running from a local folder, there is no problem. Also including the list of app.commandLine stuff from hhhuut above solves it, but also disables a lot of gpu related things which you may not want. |
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! |
I still have the following error on the latest version 28.1.0 electron, when the module is placed on a UNC path on Windows.
|
Just adding my 2 cents here, had the same problem using windows 10 and WSL 2.0. Running the project from bash installed on windows instead of WSL, worked. As mentioned by @HasseM
|
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! |
bump |
To clarify: It also does not work when running from a mapped network drive? Not a UNC path, a real mapped drive? |
Same issue here, and yes, only from mapped drive. Same drive unmapped works fine, using portable mode. |
The bug is caught by the Chromium source code FYI: |
Preflight Checklist
Electron Version
16.0.1, 15.1.2, 14.1.1, 13.1.7, 12.2.1, 11.5.0, 10.4.7,
What operating system are you using?
Windows
Operating System Version
Windows 10 version 10.0.18363 Build 18363
What arch are you using?
x64
Last Known Working Electron version
9.4.4
Expected Behavior
Created a demo electron app
with electron version>=10
and generated the exe with electron-builder. When I opened the app, the app should be launched without any error.Actual Behavior
Created a demo electron app
with electron version>=10
and generated the exe with electron-builder. When I opened the app, the app failed to launch with below error,Though the app didn't launch, in the taskbar, two processes were running in the background processes.
Testcase Gist URL
No response
Additional Information
System Info:
Here is my source code,
index.js:
index.html:
package.json:
Workaround:
It works fine, when I open the app with
--no-sandbox
or--disable-gpu-sandbox
.The text was updated successfully, but these errors were encountered: