Forum Discussion
Windows 10 - High Runtime Broker Memory Utilisation
I have searched and read the "official" page on the topic. Runtime Broker is using too much memory (microsoft.com)
However, killing the process and restarting is only a temporary solution and does not actually assist in understanding what the issue that is causing the memory use/hold/leak or whatever is happening. It takes varying lengths of time but almost always.
1 Reply
You're correct that "Runtime Broker" can sometimes consume excessive memory or CPU resources, and simply ending and restarting the process is only a temporary fix. To get to the root of the issue, it helps to understand what might be causing Runtime Broker to behave abnormally.
