forge icon indicating copy to clipboard operation
forge copied to clipboard

Startup stalled at " Launching dev servers for renderer process code"

Open FuzzyBoots opened this issue 2 years ago • 3 comments

Pre-flight checklist

  • [X] I have read the contribution documentation for this project.
  • [X] I agree to follow the code of conduct that this project uses.
  • [X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version

6.0.4

Electron version

v21.1.0

Operating system

Windows 10 Enterprise

Last known working Electron Forge version

6.0.0

Expected behavior

Running "npm start" on our application should launch the application with minimal delay.

Actual behavior

The process is stalling on launching the dev servers.

$ npm start

[email protected] start electron-forge start

[STARTED] Checking your system [STARTED] Checking git exists [STARTED] Checking node version [STARTED] Checking packageManager version [TITLE] Found [email protected] [SUCCESS] Found [email protected] [TITLE] Found [email protected] [SUCCESS] Found [email protected] [TITLE] Found [email protected] [SUCCESS] Found [email protected] [SUCCESS] Checking your system [STARTED] Locating application [SUCCESS] Locating application [STARTED] Loading configuration [SUCCESS] Loading configuration [STARTED] Preparing native dependencies [TITLE] Preparing native dependencies [SUCCESS] Preparing native dependencies [STARTED] Running generateAssets hook [SUCCESS] Running generateAssets hook [STARTED] [plugin-webpack] Compiling main process code [SUCCESS] [plugin-webpack] Compiling main process code [STARTED] [plugin-webpack] Launching dev servers for renderer process code

This last step does not complete, even when leaving it there for hours, while it lasts mere seconds for my co-workers. If I cancel it, I get a series of RpcExitError events suggesting a memory issue.

RpcExitError: Process 26472 exited with code 3221225786 Issues checking service aborted - probably out of memory. Check the memoryLimit option in the ForkTsCheckerWebpackPlugin configuration. If increasing the memory doesn't solve the issue, it's most probably a bug in the TypeScript. RpcExitError: Process 21064 exited with code 3221225786 Issues checking service aborted - probably out of memory. Check the memoryLimit option in the ForkTsCheckerWebpackPlugin configuration. If increasing the memory doesn't solve the issue, it's most probably a bug in the TypeScript. RpcExitError: Process 16756 exited with code 3221225786 Issues checking service aborted - probably out of memory. Check the memoryLimit option in the ForkTsCheckerWebpackPlugin configuration. If increasing the memory doesn't solve the issue, it's most probably a bug in the TypeScript. RpcExitError: Process 27208 exited with code 3221225786 Issues checking service aborted - probably out of memory. Check the memoryLimit option in the ForkTsCheckerWebpackPlugin configuration. If increasing the memory doesn't solve the issue, it's most probably a bug in the TypeScript.

This issue suggests that this might be a spurious error.

Steps to reproduce

Unfortunately, I am unsure as to how to replicate this, because I am unable to replicate this on my coworkers' machines.

Additional information

I get no additional information when running with "DEBUG=electron-forge:*"

FuzzyBoots avatar Feb 06 '23 15:02 FuzzyBoots

I have the same issue, when launching from vscode

bemon avatar Feb 08 '23 00:02 bemon

I ran into this same issue. However, for me npm start does work for me. It was only VSCode launching through the debugger that would get stuck at "Launching dev servers for renderer process code".

If you are using VSCode and the launch.json config from Electron Forge Debugging try adding "console": "integratedTerminal" to the config to get it to launch in the terminal instead of the Debug Console in VSCode. This worked for me.

I am not sure why the Debug Console does not work. But I found this in a possibly related issue from 2022.

Final modified config:

{
  "type": "node",
  "request": "launch",
  "name": "Electron Main",
  "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/electron-forge-vscode-nix",
  "windows": {
    "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/electron-forge-vscode-win.cmd"
  },
  // runtimeArgs will be passed directly to your Electron application
  "runtimeArgs": [
    "foo",
    "bar"
  ],
  "cwd": "${workspaceFolder}",
  "console":"integratedTerminal"
}

e8-JoshBraun avatar Mar 26 '23 17:03 e8-JoshBraun

Top level await could cause it error

Module format "cjs" does not support top-level await. Use the "es" or "system" output formats rather.
file: /Users/himself65/Code/evw/examples/evw-electron-demo/src/preload.ts

himself65 avatar Jul 11 '25 03:07 himself65