what is runtime broker, and why does it use so much memory?

Anonymous
2012-10-28T14:43:19+00:00

in task manager there is process called Runtime Broker. and it uses over 600 MB of my ram. putting my average usage at 60% on my 4 gig laptop. not noticed any performance issues yet. just a lot memory being used. makes me think of windows vista almost bc it had same issue in past. it would use all system resources.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

134 answers

Sort by: Most helpful
  1. Anonymous
    2012-10-28T19:58:36+00:00

    Hello, 

    I am facing this problem too (that is, if it is one). What I have found is that it is some sort of a security feature implemented by Microsoft in Windows 8, that monitors how metro apps use personal information and their related permissions. (Source- http://www.groovypost.com/howto/runtimebroker-exe-process-windows-8-running/)

    I would like some help as well as it does take up a lot of memory though I haven't yet seen much changes in performance.

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2012-10-30T03:56:21+00:00

    well hopefully Microsoft releases an update to fix the memory leak. shouldn't be to hard right?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2012-10-29T06:43:36+00:00

    I also have this problem but much worse - runtime broker was using 2.97 GB of memory when I checked so I killed the process (And yes, that amount of memory usage is definitely a problem!). According to articles I have read, it is supposed to have a very small memory footprint... I'd really like to know when this issue is going to be addressed by Microsoft.  

    As far as I am aware, I was not even running any Windows Runtime apps at the time, I was on the desktop using Word, Excel, Mozilla Thunderbird, VLC, Skype, Opera and Explorer. Normal physical memory usage for Windows 7 under similar conditions was around 2.5 GB at most, now it's nearly 6 GB and half of that was taken by Runtime Broker.

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2012-10-29T20:38:55+00:00

    Hello again,

    You are right. This has become a great problem now. I have done further research and have found that runtime broker and its memory related issues are due to apps with faulty codes that result in memory leaks. The source of memory leaks are very difficult to find. However since my windows installation is relatively new, I have tried uninstalling my apps one by one, and have zeroed in on my antivirus software (Bitdefender total security 2013). I uninstalled it and the runtime broker's memory usage improved immensely (it held at a max memory of 60 mb).

    I reinstalled it and almost immediately RUNTIME BROKER's memory usage kept rising. Therefore I guess it is safe to assume that it is my antivirus software which is causing the problem. However since I have already purchased this product, I have no option but to report this problem.

    I hope this helps to an extent. What antivirus solution do you use?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2012-10-30T03:50:56+00:00

    Hi,

    I'm using Norton Internet Security and I have 500 days left on my subscription so I really hope you're not right!

    So the runtime broker manages memory for applications that do not target the Windows Runtime as well as those that do? I thought it was only for new apps that ran in the metro interface...

    I will see if removing NIS makes any difference on my machine but like you, I'll just have to live with it if it does.

    I have had some other issues with metro-style apps not starting and reverting to the start menu when I open them but that's probably unrelated to this issue so I won't go into details here. I guess we have to expect a few teething problems although having said that, these kind of problems should have been ironed out before it was RTM'd.

    0 comments No comments