Discord crashed after updating to #1.6.1
dyanakiev opened this issue · comments
Yup, I got this screen too during development, but I did not find a way to reproduce it so I could not fix it
I can look into fixing it when someone finds a way to reproduce it consistently
Mine just crashed again after receiving notification in background
Mine just crashed again after receiving notification in background
I could not reproduce it on my mac, could you open the developer tools inside Discord and copy/paste the console logs inside a pastebin and post it there the next time it happens ?
Same thing here. Sorry no logs.
I managed to get it to crash to get the logs :
Crash logs
1777bb820649621c6f44.js:130 DOMException: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.
at Cs (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5988:710)
at Cs (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5988:783)
at Cs (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5988:783)
at Cs (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5988:783)
at Rs (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5988:221)
at Bu (https://discord.com/assets/0f7845e8bf9abd890fc9.js:6001:570)
at t.unstable_runWithPriority (https://discord.com/assets/0f7845e8bf9abd890fc9.js:6239:828)
at Ki (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5940:117)
at Vu (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5999:668)
at Au (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5995:382)
at https://discord.com/assets/0f7845e8bf9abd890fc9.js:5940:340
at t.unstable_runWithPriority (https://discord.com/assets/0f7845e8bf9abd890fc9.js:6239:828)
at Ki (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5940:117)
at Xi (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5940:285)
at qi (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5940:220)
at Ou (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5995:485)
at Function.e.emitChanges (https://discord.com/assets/0f7845e8bf9abd890fc9.js:4011:345)
at e.t._dispatch (https://discord.com/assets/0f7845e8bf9abd890fc9.js:4000:229)
at e.t.dispatch (https://discord.com/assets/0f7845e8bf9abd890fc9.js:3999:582)
at e.t.dirtyDispatch (https://discord.com/assets/0f7845e8bf9abd890fc9.js:3999:541)
at t.<anonymous> (https://discord.com/assets/0f7845e8bf9abd890fc9.js:2798:28)
at t.a.emit (https://discord.com/assets/0f7845e8bf9abd890fc9.js:4883:915)
at t.n._handleDispatch (https://discord.com/assets/0f7845e8bf9abd890fc9.js:1720:697)
at https://discord.com/assets/0f7845e8bf9abd890fc9.js:1718:860
at r._onDataReady (https://discord.com/assets/0f7845e8bf9abd890fc9.js:1718:340)
at r.l.push.t.handleFlushEnd (https://discord.com/assets/0f7845e8bf9abd890fc9.js:1709:251)
at d.push (https://discord.com/assets/0f7845e8bf9abd890fc9.js:5683:720)
at r.l.push.t.feed (https://discord.com/assets/0f7845e8bf9abd890fc9.js:1708:662)
at WebSocket.<anonymous> (https://discord.com/assets/0f7845e8bf9abd890fc9.js:1718:405)
I'm currently pushing an experimental fix to try and see if we still get those crashes
Mine just crashed again after receiving notification in background
I could not reproduce it on my mac, could you open the developer tools inside Discord and copy/paste the console logs inside a pastebin and post it there the next time it happens ?
Here's what I got after getting a notification in the background while browsing another app:
Mine just crashed again after receiving notification in background
I could not reproduce it on my mac, could you open the developer tools inside Discord and copy/paste the console logs inside a pastebin and post it there the next time it happens ?
Here's what I got after getting a notification in the background while browsing another app:
Thanks! These errors are actually Electron complaining about Discord not providing the map files, useful to debug their code, so they are not related to this issue, but thank you for your help :)
Just released version 1.6.2 with an attempt to fix these crashes
If you want to update, you can quit Discord entirely (by right clicking on it in your dock) and launch it again to trigger an update check
I'll let this issue open for a few days to confirm these crashes does not happen anymore