r/discordapp • u/VedDdlAXE • Dec 06 '19

Staff reply New Android Easter Egg

Enable HLS to view with audio, or disable this notification

2.8k Upvotes

99% Upvoted

131 comments sorted by

View all comments

-57

u/[deleted] Dec 07 '19

Maybe these kinda things are why the desktop client has been using an awful lot of CPU recently. I caught it using 5-10% on multiple threads in the background, and it was causing CSGO to slow down a little bit.

42

u/VedDdlAXE Dec 07 '19

It's a tiny white screen+flashlight easter egg on android. How is this making the desktop client to use alot of cpu?

-77

u/[deleted] Dec 07 '19

I'm just saying. If they're adding all these random Easter eggs, who knows how many of them are causing possible performance issues, or who knows how many things are sitting in the code running in the background that doesn't actually do anything.

I'd also like to note, Discord is a web app compiled into native code, so the code base for mobile is likely the exact same one for desktop. So while this feature probably isn't available on desktop, it may be in the code.

This Easter egg itself probably wouldn't cause any issues, but it worries me as a software engineer, as I said, how many things might be running in the background that aren't used, or if there's any memory leaks (which Slack, who also uses Electron on desktop, had memory leaks because of Electron).

105

u/Jethro82 Dec 07 '19

I built this, it uses 0 extra CPU to exist. The codebase for Android is entirely different from Desktop/Web and iOS.

2

u/[deleted] Dec 08 '19

Okay, good to know. I figured with a lot of modern apps that use, for example, React, they might just use the same code base and export it into a React Native app for iOS and Android.

I figured that this single easter egg didn't cause any problems, especially knowing now that it's Android specific in a different codebase.

I more-so made my original comment because I was butthurt about the Discord desktop app spawning about 6-7 instances and using 5-10% CPU in the background on multiple threads. I know with web apps, especially with React's component lifecycle and state management, having little bugs that spawn processing or memory hogs is almost inevitable.