[Bug]: App launch failed with error- "gpu process launch failed: error_code=40" #32074

raivekhan · 2021-12-01T11:03:32Z

Preflight Checklist

I have read the Contributing Guidelines for this project.
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for a feature request that matches the one I want to file, without success.

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,

[2752:1201/155923.159:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=40
[2752:1201/155923.268:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=40
[2752:1201/155923.346:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=40
[2752:1201/155923.424:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=40
[2752:1201/155923.502:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=40
[2752:1201/155923.580:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=40
[2752:1201/155923.659:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=40
[2752:1201/155923.737:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=40
[2752:1201/155923.815:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=40
[2752:1201/155923.815:FATAL:gpu_data_manager_impl_private.cc(417)] GPU process isn't usable. Goodbye.

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:

OS Name	: Microsoft Windows 10 Enterprise N
Version: 10.0.18363 Build 18363
Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2601 Mhz, 4 Core(s), 8 Logical Processor(s)
Adapter Type: Intel(R) HD Graphics Family, Intel Corporation compatible
Adapter Description: Intel(R) HD Graphics 530

Here is my source code,

index.js:

const { app, BrowserWindow } = require('electron')
const path = require('path');

function createWindow () {
  const win = new BrowserWindow({
    width: 800,
    height: 600,
    webPreferences: {
      preload: path.join(__dirname, 'preload.js'),
      devTools: true,
    }
  })

  win.loadFile('index.html');
};

app.whenReady().then(() => {
    createWindow()
  });

app.on('window-all-closed', function () {
    if (process.platform !== 'darwin') app.quit()
  });

index.html:

<!DOCTYPE html>
<html>
  <head>
    <meta charset="UTF-8">
    <!-- https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP -->
    <meta http-equiv="Content-Security-Policy" content="default-src 'self'; script-src 'self'">
    <meta http-equiv="X-Content-Security-Policy" content="default-src 'self'; script-src 'self'">
    <title>Hello World!</title>
  </head>
  <body>
    <h1>Hello World!</h1>
    We are using Node.js <span id="node-version"></span>,
    Chromium <span id="chrome-version"></span>,
    and Electron <span id="electron-version"></span>.
  </body>
</html>

package.json:

{
  "name": "DemoApp_Ev-16.0.1",
  "version": "1.0.0",
  "description": "This is for testing launch issue",
  "main": "index.js",
  "author": "Naimur",
  "license": "MIT",
  "scripts": {
    "start": "electron .",
    "pack": "electron-builder --dir",
    "dist": "electron-builder",
    "package": "electron-packager ./ --all"
  },
  "devDependencies": {
    "@electron-forge/cli": "^6.0.0-beta.61",
    "electron": "^16.0.1",
    "electron-builder": "^22.14.5",
    "electron-packager": "^15.4.0"
  },
  "build": {
    "appId": "naimur.test.11",
    "mac": {
      "category": "naimur.test.11"
    }
  }
}

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:

zerooverture · 2022-01-26T09:11:57Z

I have the same problem as you,It works with --disable-gpu-sandbox, but the Chrome Extensions background page doesn't work

nornagon · 2022-01-26T22:09:23Z

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.

RohitRawat12 · 2022-02-02T19:13:52Z

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

nornagon · 2022-02-02T19:32:38Z

@RohitRawat12 my snippet shows you how to collect a crash dump. If you supply the crash dump, I may be able to help further.

shugen002 · 2022-02-08T11:24:22Z

Crashpad.zip
electron: 16.0.2
I have similar problem and I use your snippet code get this dump from my user.

hhhuut · 2022-02-08T18:27:17Z

A handful of our customers (all on Win10) report the same problem, the logs look like the following:

[12836:0208/171448.703:ERROR:gpu_process_host.cc(973)] GPU process launch failed: error_code=18
[12836:0208/171448.703:WARNING:gpu_process_host.cc(1284)] The GPU process has crashed 1 time(s)
[12836:0208/171448.727:ERROR:gpu_process_host.cc(973)] GPU process launch failed: error_code=18
[12836:0208/171448.727:WARNING:gpu_process_host.cc(1284)] The GPU process has crashed 2 time(s)
[12836:0208/171448.740:ERROR:gpu_process_host.cc(973)] GPU process launch failed: error_code=18
[12836:0208/171448.740:WARNING:gpu_process_host.cc(1284)] The GPU process has crashed 3 time(s)
[12836:0208/171448.744:ERROR:gpu_process_host.cc(973)] GPU process launch failed: error_code=18
[12836:0208/171448.744:WARNING:gpu_process_host.cc(1284)] The GPU process has crashed 4 time(s)
[12836:0208/171448.765:ERROR:gpu_process_host.cc(973)] GPU process launch failed: error_code=18
[12836:0208/171448.765:WARNING:gpu_process_host.cc(1284)] The GPU process has crashed 5 time(s)
[12836:0208/171448.777:ERROR:gpu_process_host.cc(973)] GPU process launch failed: error_code=18
[12836:0208/171448.777:WARNING:gpu_process_host.cc(1284)] The GPU process has crashed 6 time(s)
[12836:0208/171448.779:ERROR:gpu_process_host.cc(973)] GPU process launch failed: error_code=18
[12836:0208/171448.779:WARNING:gpu_process_host.cc(1284)] The GPU process has crashed 7 time(s)
[12836:0208/171448.804:ERROR:gpu_process_host.cc(973)] GPU process launch failed: error_code=18
[12836:0208/171448.804:WARNING:gpu_process_host.cc(1284)] The GPU process has crashed 8 time(s)
[12836:0208/171448.813:ERROR:gpu_process_host.cc(973)] GPU process launch failed: error_code=18
[12836:0208/171448.813:WARNING:gpu_process_host.cc(1284)] The GPU process has crashed 9 time(s)
[12836:0208/171448.813:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.

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 --no-sandbox flag works for those customers as well, and I'll try to get my hands on a crash dump from them in the near future.

hhhuut · 2022-02-09T07:54:35Z

Update: The --no-sandbox flag did not resolve the problem for our users, the application kept on crashing.

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).

Crashdumps.zip

I hope this issue can be solved quickly since I didn't find any more workarounds we could try.

hhhuut · 2022-02-10T09:00:02Z

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.

Crashdumps2.zip

aleksandrs94 · 2022-02-10T10:13:01Z

Hi, just started to use electron and it looks like I'm getting into same problem. I'm able to run app with --no-sandbox flag though. Please find a zip with crashdump, hope it helps :)

Crashpad.zip

hhhuut · 2022-02-16T06:41:42Z

And again new crashdumps from two more of our users.
Crashdumps3.zip

hhhuut · 2022-02-17T13:59:32Z

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.

app.commandLine.appendSwitch('no-sandbox');
app.commandLine.appendSwitch('disable-gpu');
app.commandLine.appendSwitch('disable-software-rasterizer');
app.commandLine.appendSwitch('disable-gpu-compositing');
app.commandLine.appendSwitch('disable-gpu-rasterization');
app.commandLine.appendSwitch('disable-gpu-sandbox');
app.commandLine.appendSwitch('--no-sandbox');
app.disableHardwareAcceleration();

I'm not sure which specific one does the trick, however as stated previously, just adding the app.commandLine.appendSwitch('no-sandbox'); switch was not enough.

Hope that info helps a little, in conjunction with the crash reports.

zerooverture · 2022-02-21T06:38:12Z

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

hhhuut · 2022-03-10T15:10:48Z

Bump: Has there been any progress on evaluating this particular problem and the crashreports?

shugen002 · 2022-03-15T03:00:34Z

@nornagon any progress ? or any more specify information we need to collect from our client ?

epelc · 2022-06-14T19:09:12Z

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 no-sandbox or disable-gpu-sandbox flags allowed the app to run. It worked fine on a regular windows machine(x64) without these flags. It also works fine on macOS without the flags.

app.commandLine.appendSwitch('disable-gpu-sandbox')

I think disable-gpu-sandbox would be preferred to no-sandbox entirely.

Edit strike that, only using disable-gpu-sandbox makes it so the dev tools cannot be opened in any way. You need to use no-sandbox to get the devtools to show.

mikehearn · 2022-11-02T10:42:33Z

I think there are several different issues being conflated here due to the similar error messages.

error_code=18 is SBOX_ERROR_CREATE_PROCESS and means that CreateProcess itself failed, so yeah it'd be expected that we don't see any crash dump data from the gpu process - it never started at all. Error 18 can be caused by running an Electron app from some kinds of non-local / mapped network drive. For example, if you try to run an Electron Windows app inside Parallels from a drive mapped to your Mac, you will get this error.

error_code=40 is SBOX_ERROR_CANNOT_SETUP_INTERCEPTION_THUNK which indicates the GPU process started, but the sandbox was unable to complete the setup process. I don't know what can cause this.

In both cases they indicate something very low level and not necessarily GPU specific has gone wrong.

dohooo · 2022-11-21T12:42:31Z

Any update are their?

war59312 · 2023-02-03T19:57:32Z

FYI @ https://oofhours.com/2023/02/02/samsung-magician-wont-launch-heres-a-simple-fix/

kiddailey · 2023-02-07T04:42:24Z

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.

github-actions · 2023-05-09T01:55:18Z

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!

uncaught · 2023-05-20T10:45:57Z

Still an issue - I'm new to electron, but the initial setup you get when running npm init electron-app@latest my-app -- --template=webpack-typescript already does not work at all. Keeps crashing with these GPU errors.

I'm on Windows 11 with WSL

jbeetle · 2023-05-31T10:46:46Z

have the same err in windows11

YourGirlInSpace · 2023-08-18T14:50:28Z

I have a similar error in Arch Linux kernel version 6.4.7-arch1-1:

[1185259:0818/070037.216495:ERROR:zygote_communication_linux.cc(291)] Failed to send GetTerminationStatus message to zygote
[1185259:0818/070037.219115:ERROR:gpu_process_host.cc(985)] GPU process launch failed: error_code=1002
...
[1185259:0818/070037.219442:FATAL:gpu_data_manager_impl_private.cc(440)] GPU process isn't usable. Goodbye.

Where are these error codes defined? This may give clues on what's going on.

ej-toita · 2023-08-25T02:46:10Z

I experienced a similar error when the executable is placed on a network folder (a UNC path).

in my case app.commandLine.appendSwitch('disable-gpu-sandbox'); solved the error, but this is undesireble because this may cause a security risk.

I am pretty sure that the error is related to chromium
https://chromium.googlesource.com/chromium/chromium/+/master/content/public/common/content_switches.cc#118

HasseM · 2023-09-23T12:14:47Z

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.

electron-issue-triage · 2023-12-25T01:49:57Z

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!

ej-toita · 2023-12-27T03:39:38Z

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.

[32140:1227/123812.304:ERROR:gpu_process_host.cc(987)] GPU process launch failed: error_code=18
[32140:1227/123812.360:ERROR:gpu_process_host.cc(987)] GPU process launch failed: error_code=18
[32140:1227/123812.380:ERROR:gpu_process_host.cc(987)] GPU process launch failed: error_code=18
[32140:1227/123812.402:ERROR:gpu_process_host.cc(987)] GPU process launch failed: error_code=18
[32140:1227/123812.421:ERROR:gpu_process_host.cc(987)] GPU process launch failed: error_code=18
[32140:1227/123812.440:ERROR:gpu_process_host.cc(987)] GPU process launch failed: error_code=18
[32140:1227/123812.460:ERROR:gpu_process_host.cc(987)] GPU process launch failed: error_code=18
[32140:1227/123812.478:ERROR:gpu_process_host.cc(987)] GPU process launch failed: error_code=18
[32140:1227/123812.498:ERROR:gpu_process_host.cc(987)] GPU process launch failed: error_code=18
[32140:1227/123812.498:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.

IaveL · 2023-12-28T00:53:59Z

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

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.

electron-issue-triage · 2024-03-28T01:48:14Z

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!

wusticality · 2024-04-09T02:59:03Z

bump

Hrxn · 2024-05-11T17:40:26Z

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.

To clarify:

It also does not work when running from a mapped network drive? Not a UNC path, a real mapped drive?

arthurgailes · 2024-05-14T14:47:55Z

Same issue here, and yes, only from mapped drive. Same drive unmapped works fine, using portable mode.

raivekhan added the bug 🪲 label Dec 1, 2021

hal2100 mentioned this issue Jan 6, 2022

GPU process launch failed: error_code=18 altair-graphql/altair#1688

Closed

martpie mentioned this issue Jan 7, 2022

Not opening in fedora 35 martpie/museeks#630

Closed

tbiethman mentioned this issue Jan 26, 2022

Windows 10_Getting an error "GPU process launch failed: error_code=18" while trying to open cypress test runner. cypress-io/cypress#19924

Closed

vbogach mentioned this issue Mar 31, 2022

VSCode stopped opening - The GPU process has crashed microsoft/vscode#146464

Closed

JoseALermaIII mentioned this issue Apr 11, 2022

Portable Mode in Windows 10 mapped network drive doesn't launch after upgrade from 1.65.2 to 1.66.1 microsoft/vscode#147174

Closed

fredrikhr added a commit to fredrikhr/s-KaiNet-node-sp-auth that referenced this issue Jun 9, 2022

Add electron switch no-sandbox, addressing electron/electron#32074

ad972be

fredrikhr mentioned this issue Jun 9, 2022

On-demand fix s-KaiNet/node-sp-auth#108

Merged

2 tasks

marc2332 mentioned this issue Jun 10, 2022

GPU process isn't usable. Goodbye. Graviton-Code-Editor/Graviton-App#327

Closed

snyk-bot mentioned this issue Aug 14, 2022

[Snyk] Security upgrade node-sp-auth from 3.0.4 to 3.0.6 koltyakov/sppull#63

Open

koltyakov mentioned this issue Aug 14, 2022

[Snyk] Security upgrade node-sp-auth from 3.0.4 to 3.0.6 koltyakov/sppurge#22

Merged

dohooo mentioned this issue Nov 21, 2022

Cannot open the .exe file after compiling on mac. cawa-93/vite-electron-builder#873

Closed

Molunerfinn mentioned this issue Nov 29, 2022

[Bug]: 启动一次程序产生多个进程并占用大量CPU资源 Molunerfinn/PicGo#1029

Closed

3 tasks

github-actions bot added the stale label May 9, 2023

github-actions bot removed the stale label May 21, 2023

electron-issue-triage bot added the stale label Dec 25, 2023

electron-issue-triage bot removed the stale label Dec 28, 2023

1111mp mentioned this issue Jan 5, 2024

有可能支持Arm版windows系统吗，现在的情况是能安装但是打不开 1111mp/nvm-desktop#38

Closed

mifi mentioned this issue Feb 15, 2024

Can't run from network drive. GPU process isn't usable. Goodbye. mifi/lossless-cut#1893

Closed

5 tasks

danielgp mentioned this issue Feb 22, 2024

[Snyk] Security upgrade node-sp-auth from 3.0.0 to 3.0.6 danielgp/sharepoint-extractor#54

Merged

electron-issue-triage bot added the stale label Mar 28, 2024

RunDevelopment mentioned this issue Apr 8, 2024

Fails to start chaiNNer-org/chaiNNer#2607

Open

electron-issue-triage bot removed the stale label Apr 10, 2024

codebykat mentioned this issue May 9, 2024

Fixed app start up issue on Linux (Ubuntu) Automattic/simplenote-electron#3159

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug]: App launch failed with error- "gpu process launch failed: error_code=40" #32074

[Bug]: App launch failed with error- "gpu process launch failed: error_code=40" #32074

raivekhan commented Dec 1, 2021 •

edited

zerooverture commented Jan 26, 2022

nornagon commented Jan 26, 2022

RohitRawat12 commented Feb 2, 2022

nornagon commented Feb 2, 2022

shugen002 commented Feb 8, 2022 •

edited

hhhuut commented Feb 8, 2022 •

edited

hhhuut commented Feb 9, 2022

hhhuut commented Feb 10, 2022

aleksandrs94 commented Feb 10, 2022

hhhuut commented Feb 16, 2022

hhhuut commented Feb 17, 2022 •

edited

zerooverture commented Feb 21, 2022

hhhuut commented Mar 10, 2022

shugen002 commented Mar 15, 2022

epelc commented Jun 14, 2022 •

edited

mikehearn commented Nov 2, 2022

dohooo commented Nov 21, 2022

war59312 commented Feb 3, 2023

kiddailey commented Feb 7, 2023

github-actions bot commented May 9, 2023

uncaught commented May 20, 2023

jbeetle commented May 31, 2023

YourGirlInSpace commented Aug 18, 2023

ej-toita commented Aug 25, 2023 •

edited

HasseM commented Sep 23, 2023

electron-issue-triage bot commented Dec 25, 2023

ej-toita commented Dec 27, 2023

IaveL commented Dec 28, 2023

electron-issue-triage bot commented Mar 28, 2024

wusticality commented Apr 9, 2024

Hrxn commented May 11, 2024

arthurgailes commented May 14, 2024

[Bug]: App launch failed with error- "gpu process launch failed: error_code=40" #32074

[Bug]: App launch failed with error- "gpu process launch failed: error_code=40" #32074

Comments

raivekhan commented Dec 1, 2021 • edited

Preflight Checklist

Electron Version

What operating system are you using?

Operating System Version

What arch are you using?

Last Known Working Electron version

Expected Behavior

Actual Behavior

Testcase Gist URL

Additional Information

index.js:

index.html:

package.json:

Workaround:

zerooverture commented Jan 26, 2022

nornagon commented Jan 26, 2022

RohitRawat12 commented Feb 2, 2022

nornagon commented Feb 2, 2022

shugen002 commented Feb 8, 2022 • edited

hhhuut commented Feb 8, 2022 • edited

hhhuut commented Feb 9, 2022

hhhuut commented Feb 10, 2022

aleksandrs94 commented Feb 10, 2022

hhhuut commented Feb 16, 2022

hhhuut commented Feb 17, 2022 • edited

zerooverture commented Feb 21, 2022

hhhuut commented Mar 10, 2022

shugen002 commented Mar 15, 2022

epelc commented Jun 14, 2022 • edited

mikehearn commented Nov 2, 2022

dohooo commented Nov 21, 2022

war59312 commented Feb 3, 2023

kiddailey commented Feb 7, 2023

github-actions bot commented May 9, 2023

uncaught commented May 20, 2023

jbeetle commented May 31, 2023

YourGirlInSpace commented Aug 18, 2023

ej-toita commented Aug 25, 2023 • edited

HasseM commented Sep 23, 2023

electron-issue-triage bot commented Dec 25, 2023

ej-toita commented Dec 27, 2023

IaveL commented Dec 28, 2023

electron-issue-triage bot commented Mar 28, 2024

wusticality commented Apr 9, 2024

Hrxn commented May 11, 2024

arthurgailes commented May 14, 2024

raivekhan commented Dec 1, 2021 •

edited

shugen002 commented Feb 8, 2022 •

edited

hhhuut commented Feb 8, 2022 •

edited

hhhuut commented Feb 17, 2022 •

edited

epelc commented Jun 14, 2022 •

edited

ej-toita commented Aug 25, 2023 •

edited