But it's still quite easy to join an active community. Great choice for a platform.Unfortunately, you can't browse for servers to join on the Discord app itself. Skype, discord, steam, slack and what not. That would take less space because it would use a single master instance.Īpps that need to run in the background are using embedded browsers. Honestly it would just be better to run all those apps in the browser as tabs. 20~50MB memory? But every single electron app is now running their own master instance of chrome embed.
BETTER DISCORD FOR MAC CODE
You could easily have listviews hosting server icons and friendlists, another listview for chat threads, and on native code the same would take what.
BETTER DISCORD FOR MAC FULL
You're running a full fledged browser all because you need certain fixed functions. Sure it's less hassle for developers to make for cross platform, but it's absolutely horrible when it comes to resources. Every single app has gone chrome-embedded these days. If it weren't for discord's convenience I would absolutely not use it. The command-line arguments on those child processes pretty much explain it. So maybe it's an issue with the pulse-audio? After a complete systemreboot my discord now seems to be working stable (none of the cpus goes above 40%, no crashing, no lagging). I will try another display-manager, but i am not very positive, that this will change anything.Įdit: changing the display-manager did not solve the problem but i changed something in the pulse audio (i'm sorry i don't know what i did anymore) and forgot to reboot, my discord died of high cpu-usage again after that. The problem started with some discord-update (not sure which one) on ubuntu 20.04, i changed to 20.10 (beta) but the problem persists (no change at all). Yesterday i had a long voicechat and didn't check the chat until i realised one of my cpus was at 100% usage (all others were idling at 2-5%) it took about 10-20 minutes until discord finally decided to crash. After changing to discord_canary i though my problem was gone but i wasn't in voice-chats for long. I turned harware-acceleration on (which seemed to make it worse),turned it back off, tried to turn off different other options, none of that changed anything.
Randomly after it tries to eat up one of my cpu-cores it crashes and the whole problem starts again. Strange thing is it does not seem to affect other programs and while in the voice-chat i can hear everyone perfectly clear no matter how unresponsive my discord-app gets. Sometimes it starts climbing really high after minutes, sometime it takes hours to even get unresponsive. Discord does not seem to use all of my CPU-cores but uses one core up to 100(!)% starting discord its arround 10%, the longer the voice-chat is running the higher the cpu-usage climbs.
It starts with the chat getting very unresponsive and laggy but it does not stop at 40% CPU-usage for me. I only have the CPU-Problem in a voice-chat. If that still doesn't help, can you try these pre-release versions of the desktop client instead?Īlso, to help me isolate the issue, are you in a fairly active server with lots of images and/or constant chats being sent? Does this also happen when using voice chat, or even when not connected to voice? If it's already on, or turning it on doesn't help, can you try a clean reinstall of the app by following the steps found in this article: Make sure to close all Discord processes via Task Manager and double-check those AppData folders shown in the article, as well as turn off your antivirus and firewalls before reinstalling. Thanks for reaching out! The app shouldn't be using that much CPU for extended periods, though.įor starters, can you head into your User Settings > Appearance page and make sure that Hardware Acceleration is turned on?
0 kommentar(er)
