
- #Why does slack client have so many processes windows 8
- #Why does slack client have so many processes windows
Make sure the app is updated to the latest version.

If that’s the case, you’ll have to narrow down the app that’s causing the problem. It’s also possible that you have a misbehaving app that’s causing Runtime Broker to use more resources than it should. Head to Settings > System > Notifications & Actions, and then turn off the “Get tips, tricks, and suggestions as you use Windows” option. For whatever reason, this activity behaves like a universal app and engages the Runtime Broker process.
#Why does slack client have so many processes windows
If you’ve recently upgraded to Windows 10, you may have noticed that Windows likes to show you the occasional tip via notifications. If you notice that Runtime Broker is consistently consuming 30% or more of your CPU, showing higher than expected memory usage, or spiking the usage even when you don’t have a universal app running, there are a couple of potential explanations. When you launch a universal app, that usage should briefly rise to 25-30% and then settle back down. When its just running in the background, Runtime Broker usually consumes 0% of your CPU. And when you close all open universal apps, Runtime Broker’s memory usage should drop back down to the 20-40 MB range. Launching additional universal apps should not cause Runtime Broker to consume additional memory. When you launch a universal app, you will likely see the memory usage rise to anywhere from 500-700 MB. When it’s not active, Runtime Broker maintains a very low memory profile, typically taking up around 20-40 MB. You can think of it like a middleman hooking your universal apps with the trust and privacy settings you’ve configured. Though it runs in the background all the time, you will likely see its activity rise when you launch a universal app. It is used to determine whether universal apps you got from the Windows Store–which were called Metro apps in Windows 8–are declaring all of their permissions, like being able to access your location or microphone.
#Why does slack client have so many processes windows 8
Runtime Broker is an official Microsoft core process that debuted in Windows 8 and continues in Windows 10.
