Why is my ram usage for steam and google chrome so high? Can anyone answer this?

[Sr. Pescas™]

I have 4 gigs of ram but my usage always stays at around 44 % when im not doing anything. In task manager sometimes steam.exe is at 70,000 k memory and sometimes over 100,000. And there are like ten chrome.exe ones with one at 71,000 k memory, one at 64000 k one at 40,000 k, 2 around 10,000 k and the rest under 5,000 k. Is there a reason some of these are so high and some aren't? Is there something that i need to do to fix this?

[Silicon Vampire]

It's the normal operation of your computer, there is nothing to fix.

[PLANTROON]

No there is no way to fix it. Google Chrome is a memory hog. You have many chrome.exe processes because Google Chrome runs every tab in a separate process. There are some addons as well that usually consume high amount of memory.

[Satoru]

We are not in the XP days where we have to dole out memory like it's the Depression

The OS will allocate memory as long as it's available. The more memory you have the more it will allocate to resources taht request it. That's normal.

If you start running out of memory that's a problem

But the OS is using memory, let it do it's job.

[how bout i do anyway]

If Chrome is using up too much memory for you to play a game, just close it and bring it back up later. If Steam is using up too much memory for you to do non-Steam things, close it and bring it back up later.

[Sr. Pescas™]

thank you guys for the responses

[Satoru]

Publicado originalmente por BDK:

Steam is bloat with the ocational memory leak. Bringin up the main ui and exiting it again will usually clear it, but it's not going to work all the time

That's the exact opposite of a 'memory leak'. Using memory is not a 'memory leak'.

[aiusepsi]

Publicado originalmente por BDK:

Steam is bloat with the ocational memory leak. Bringin up the main ui and exiting it again will usually clear it, but it's not going to work all the time.

Yeah, that's not a memory leak. A memory leak is where a program allocates memory, then subsequently forgets the pointer to the allocated memory so that it becomes impossible to ever deallocate it.

If it's getting deallocated, then the memory wasn't leaked, by definition.