SpacingBat3 / WebCord

A Discord and SpaceBar :electron:-based client implemented without Discord API.
MIT License
1.88k stars 93 forks source link

Webcord fails to start on Windows #436

Closed Rikj000 closed 1 year ago

Rikj000 commented 1 year ago

Aknowledgements

Operating System / Platform

🪟️ Windows

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

Can't check due to application not opening.

Application version

v4.3.0

Bug description

v4.3.0 refuses to open.

When I try to launch the .exe directly from PowerShell, following error is returned:

ERROR:crashpad_client_win.cc(844)] not connected

I get the same result with webcord.exe --verbose

Also checked Event Viewer's Application Logs,
but can't find anything related to the crash there.

Additional context

No response

Rikj000 commented 1 year ago

Linking to: https://github.com/SpacingBat3/WebCord/issues/432

HyperCriSiS commented 1 year ago

I have the same issue. Tried to start this version: WebCord-win32-x64-4.3.0.zip

I am running Windows 11. The process starts and is killed after about a second.

If I try to get the version via command line I get: [6892:0726/222032.307:ERROR:crashpad_client_win.cc(844)] not connected

How can I provide a debug log?

ShadyGalal commented 1 year ago

Same issue here. Any resolutions?

Rikj000 commented 1 year ago

@SpacingBat3 I hope these findings might be able to help resolve this issue.

I've noticed that on my Manjaro Linux system,
I'm running WebCord v4.3.0 without issues.

Perhaps it's an Electron bug, and not a WebCord bug?

Linux Environment

Software Version Source
Manjaro Linux x86_64 Kernel 5.15.120-1-MANJARO /
Electron v25.3.1 https://archlinux.org/packages/extra/any/electron/
WebCord v4.3.0 https://aur.archlinux.org/packages/webcord-bin

Windows Environment

Software Version Source
Windows 11 Pro Kernel 10.0.22621.0 /
Electron v25.4.0 https://community.chocolatey.org/packages/electron
WebCord v4.3.0 https://github.com/ScoopInstaller/Extras/blob/master/bucket/webcord.json

Note: I specifically installed Electron for this issue, and rebooted the PC afterwards, without any luck.
In the past WebCord always worked without having to install Electron.

SpacingBat3 commented 1 year ago

@Rikj000 Yes, Linux version works fine, macOS (?) and Windows seem to only crash for any reason. Also on Windows I couldn't find a way to debug what's causing the issue and currently I've found no luck running it on a newer version of Electron or under WineHQ. I'll try again with the newer versions of Electron, I believe currently v24 works fine.

Also it definitely happens to crash before even Chromium fully loads, so maybe that's when I'm applying some command-line flags to Chromium cmdline (this is possible before ready event only, after Chromium loads I doubt I can apply flags in other way than restarting the app) or parsing them?

In the past WebCord always worked without having to install Electron.

You mean electron packages on Manjaro / Arch Linux? I doubt AUR version would run without any electron package installed, I think both Hanabishi and I are packaging it to use system packages and I even made possible to (experimentally) use other dependencies provided by Arch Linux packages (e.g. marked, semver) over bundling them inside ASAR archive.

Rikj000 commented 1 year ago

In the past WebCord always worked without having to install Electron.

You mean electron packages on Manjaro / Arch Linux? I doubt AUR version would run without any electron package installed, I think both Hanabishi and I are packaging it to use system packages and I even made possible to (experimentally) use other dependencies provided by Arch Linux packages (e.g. marked, semver) over bundling them inside ASAR archive.

I mean in the past WebCord worked on Windows without explicitly installing Electron :)

SpacingBat3 commented 1 year ago

Update to Electron v26.0.0 should fix this (at least it works through WineHQ, would be really weird not to work on Windows).

ltguillaume commented 1 year ago

4.4.0 confirmed working!

Started with "I didn't crash this time!", lol.

DeathDragonAW commented 11 months ago

Still having this issue with both 4.3.0 and 4.4.0. 4.2.0 is still working.