Open Rexogamer opened 2 months ago
Observing a similar issue here. Inspecting the startup logs I see the following:
spdlog fatal error: Failed opening file discord_utils.log for writing: Permission denied
[WebContents] crashed (reason: crashed, exitCode: 134)... reloading
Optional module ./ElectronTestRpc was not included.
spdlog fatal error: Failed opening file discord_utils.log for writing: Permission denied
[WebContents] double crashed (reason: crashed, exitCode: 134)... RIP =(
I'm not sure where to go from here; spdlog is a logging library for C++, apparently used by Electron (?). I'm just not sure why it breaks in this manner when using OpenAsar.
workaround: run the app from a terminal with the --disable-logging
param (e.g. discord-canary --disable-logging
)
edit: this seems to work because it lets the app write to the log file, so the param might not actually be the fix - running Discord in a directory with write access might be the real reason why this works
[IGNORE AS ISSUE IS FIXED. NEEDED TO ALLOW DISCORD TO RUN ITS INITIAL UPDATES BEFORE REAPPLYING OPENASAR. Sorry :) ]
Same issue for me after latest discord update. Application crashes at startup. Ran discord in the terminal and same result. --disable-logging did not work for me. I reinstalled discord and no luck. I uninstalled openasar and reinstalled discord and everything works again:
even if i let canary do its initial updates before installing openasar i still crash
Yep, crashing on PTB now too, even after allowing Discord to update.
ptb 331156 (257096f) Host 0.0.137 arm64 Build Override: N/A macOS 15 (24.0.0)
Writing to say here that I am also experiencing this issue on the stable build of discord (0.0.70) on arch linux.
I also am experiencing nearly identical logs that l-zeuch provided but also with this coredump:
Oct 01 14:01:57 [...] systemd-coredump[5085]: [🡕] Process 5037 (Discord) of user 1000 dumped core.
Module [~]/.config/discord/0.0.70/modules/discord_utils/node_modules/macos-notification-state/build/Release/notificationstate.node without build-id.
Stack trace of thread 5037:
[...]
([~]/.config/discord/0.0.70/modules/discord_utils/discord_utils.node + 0x643c3)
ELF object binary architecture: AMD x86-64
And my version of the other logs:
Oct 01 15:17:45 [...] discord[15991]: Optional module ./ElectronTestRpc was not included.
Oct 01 15:17:45 [...] discord[16045]: [16045:1001/151745.282197:ERROR:ffmpeg_common.cc(965)] Unsupported pixel format: -1
Oct 01 15:17:46 [...] discord[16095]: spdlog fatal error: Failed opening file discord_utils.log for writing: Permission denied
Oct 01 15:17:46 [...] systemd-coredump[16134]: Process 16095 (Discord) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Oct 01 15:17:46 [...] systemd[1]: Started Process Core Dump (PID 16134/UID 0).
happing on stable as well macos still crashes after it does its updates...
stable 331573 (1886297)
Host 0.0.321 x64
Build Override: N/A
macOS 11 (20.6.0)
using the latest version of Discord Canary (0.0.492) and the latest version of OpenAsar, upon opening the app the main window appears for a few seconds before the whole app crashes and closes.
switching back to the default .asar file, the app works as normal.
I'm using Ubuntu 24.04.
(note that this isn't the same as #183 - this only started happening either today or yesterday, and the app doesn't open at all despite repeated attempts.)
Screencast from 2024-09-21 21-27-23.webm