Runtime broker uses too much memory

For some reason I notice that the Runtime Broker process takes up too much memory. Close to 300mb. Also I see two of them running now. I don't recall what I did but at this point its memory use slowly went down  to about 15mb. The 2nd instance is taking about 1mb. 

 

During high memory usage period the surface is not behaving properly.  It does not react to clicking links for example. Clicking a link in Mail does not bring up ie.

 

Are you aware of this?

 

Also I once killed that process and nothing bad happened.  I cannot figure out what its for.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Runtimebroker.exe is basically in charge of metro permissions.  If you have a bunch of metro apps running it will get larger.  You cant kill the process because that would kill the metro apps.

http://www.groovypost.com/howto/runtimebroker-exe-process-windows-8-running/
Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Yeah, I checked it out, but based on its behavior it looks like a runaway app can cause the runtime broker process to grow in size indefinitely affecting performance of the entire system.   A leaky app should only leak its own memory, not the memory of another process.  Bad design? 

 

One must concede, however, that it's difficult to design an OS that can sustain an impact of a really badly behaving process.  As I understand, the Store with its rigorous verification should be vetting these bad apples out.   I have a feeling that Microsoft with its over-eagerness to populate the store is causing more long-term damage to the ecosystem by compromising on the quality of the apps it's letting through into the store. Yes they get many apps quickly, but bad apps tarnish reputation of the OS.

 

Thanks for quick reply, BTW.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Had to kill it again this morning.  It was using 348mb of ram. App processes kept on running and a new runtime broker was launched using about 3mb.

 

Something is not right.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

From the Start screen type the word 'task'. Select Task Manager, then in the lower lefthand corner of Task Manager select 'More Options'. You should be able to track down the app causing the problem.
Please mark this reply as an answer if it answers your question

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You must have misunderstood. The runtime broker uses too much memory.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You must have misunderstood. The runtime broker uses too much memory.

Can you get a clue as to the leaky app in App history?
Please mark this reply as an answer if it answers your question

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I guess I am missing something.  The app that's using to much memory is not, really, an app.  It's a process called "Runtime Broker".  This process is used by other apps.  According to the ZigZag3143x, the app memory grows with the number of apps used.  But that's not the case.  I notice that the process uses a lot of memory, unrelated to the number of apps in use. 

 

Moreover, as the memory usage grows beyond reasonable, to well over 200MB, the tablet performance and functionality suffer.  Killing the process seems to restore the tablet to good state.  But I think that's a wrong way to fix things.   Therefore I started the thread.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I'm seeing this problem as well, although on an x86 instance of Windows 8 rather than a Surface.  In my case, the Runtime Broker rose to 1.5 GB and the machine became unresponsive.  Need some way to identify the offending application.  Another thread has suggested this involves a Windows Store app not handling notifications but it's unclear to me what I can do to identify the bad app.  Task Manager doesn't seem to provide a way to break out any detail here.
e

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Runtimebroker.exe is basically in charge of metro permissions.  If you have a bunch of metro apps running it will get larger.  You cant kill the process because that would kill the metro apps.

http://www.groovypost.com/howto/runtimebroker-exe-process-windows-8-running/


I think that this occurs when more than one user is logged into the system.  Keeping two users logged in overnight causes this problem in the morning. 

 

 I just tried switching from my user account to another one. That switch alone caused runtime broker to go up to 238.8mb. Microsoft please look into this urgently.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Uninstall clock apps if you have any. These apps are most prone to this fever. Hope Microsoft fixes it with an update.

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated May 5, 2020 Views 3,057 Applies to: