Webcord crashed, now crashes on startup.

[Fokke456]

Acknowledgements

• [X] I have checked that there is no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.

• [X] This bug affects Discord website.

• [ ] This issue is confirmed to be reproducible when WebCord is packaged on at least all three latest supported Electron major releases.

• [ ] This issue is reproducible in Chrome, Chromium or any Chromium-based browser, e.g Brave or Edge (please write in Additional Context which browser you have used if it is neither Chrome nor unmodified Chromium).

• [ ] There are no fixes done to master which resolves this issue.

• [ ] My issue describes one of the unstable and/or not fully implemented features.

• [ ] I have found a workaround to mitigate or temporarily fix this issue in affected releases (please write it in Additional context section below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

v29.1.1-1

Application version

v4.8.0-2

Bug description

Recently webcord crashed mid use (while I was in a call, looking at someone stream) and ever since it hasn't worked. It crashes on startup with the following dump:

/usr/lib/electron29/electron[5630]: ../../third_party/electron_node/src/node_builtins.cc:328:MaybeLocal<Function> node::builtins::BuiltinLoader::LookupAndCompileInternal(Local<Context>, const char *, std::vector<Local<String>> *, Realm *): Assertion `(this) == (optional_realm->env()->builtin_loader())' failed. 1: 0x56497ab19d46 [/usr/lib/electron29/electron /usr/lib/webcord] 2: 0x56497ab199cd [/usr/lib/electron29/electron /usr/lib/webcord] 3: 0x56497aaf6e98 [/usr/lib/electron29/electron /usr/lib/webcord] 4: 0x5649697b9471 [/usr/lib/electron29/electron /usr/lib/webcord] 5: 0x5649697b5f75 [/usr/lib/electron29/electron /usr/lib/webcord] 6: 0x56497abf11a2 [/usr/lib/electron29/electron /usr/lib/webcord] 7: 0x56496ea70fc7 [/usr/lib/electron29/electron /usr/lib/webcord] Received signal 6 #0 0x56497313ea13 (/usr/lib/electron29/electron+0xe66da12) #1 0x56497311a354 (/usr/lib/electron29/electron+0xe649353) #2 0x56497313e32b (/usr/lib/electron29/electron+0xe66d32a) #3 0x7f4760070770 (/usr/lib/libc.so.6+0x4076f) #4 0x7f47600c132c (/usr/lib/libc.so.6+0x9132b) #5 0x7f47600706c8 gsignal #6 0x7f47600584b8 abort #7 0x56497ab19d55 (/usr/lib/electron29/electron+0x16048d54) #8 0x56497ab199cd (/usr/lib/electron29/electron+0x160489cc) #9 0x56497aaf6e98 (/usr/lib/electron29/electron+0x16025e97) #10 0x5649697b9471 (/usr/lib/electron29/electron+0x4ce8470) #11 0x5649697b5f75 (/usr/lib/electron29/electron+0x4ce4f74) #12 0x56497abf11a2 (/usr/lib/electron29/electron+0x161201a1) #13 0x56496ea70fc7 (/usr/lib/electron29/electron+0x9f9ffc6) r8: 0000000000000000 r9: 0000000000000001 r10: 0000000000000008 r11: 0000000000000246 r12: 0000380c00098000 r13: 0000000000000006 r14: 00007f476020d6a0 r15: 0000380c003a0518 di: 00000000000015fe si: 00000000000015fe bp: 00007f475c93c940 bx: 00000000000015fe dx: 0000000000000006 ax: 0000000000000000 cx: 00007f47600c132c sp: 00007ffff0774190 ip: 00007f47600c132c efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] zsh: IOT instruction (core dumped) webcord

Reinstalling doesn't resolve the issue; neither does reinstalling electron29. Trying to run electron29 itself causes the same issue, though presumably webcord is at fault since it crashing caused this. Neither of the two has had an update between it functioning and it not.

Additional context

My system uses:

• Manjaro linux KDE 6.6.19-1
• Window system X11
• KDE Plasma 5.27.10

Webcord was, I believe, running on a Nvidia RTX 4060 laptop. I also have a 7840HS iGPU.

[SamuelH98]

also have this problem :| 7940hs

[brocococonut]

Reinstalling doesn't resolve the issue; neither does reinstalling electron29. Trying to run electron29 itself causes the same issue, though presumably webcord is at fault since it crashing caused this. Neither of the two has had an update between it functioning and it not.

I've found the only thing that fixes it is clearing out the cache for the app in your user directory. Buuuuuut that's only temporary, because after you open it back up, sign back in, then close it again, you come across the same issue.