Lead3 has stated the position as it should be. The reality, in my view, can be different. The statement, that
Windows will also relinquish the standby RAM, is where I have doubts. If it were always true, then why when you restart your computer do response times, which were sluggish with Standby large and Free hovering around Zero, immediately
become more lively. As you have noticed if you use RAMMap to clear Standby the result is the same as if you had restarted your computer. It can only be assumed that memory is not always released from Standby.
For years there has been an on-going debate about memory leaks. Originally there was a problem whereby 16 bit programmes did not release memory on a 32 bit system. Aside from that it has always been known that some programmes do not release memory as they
should. Browsers tend to hold on to memory and Firefox is often quoted as an example.
In the past users have devoted a lot of time trying to determine which programmes on their computer have a memory leak. The problem is that if you determine that one programme leaks what do you about it? You can complain to the software provider and publicise
your findings. You may eventually get the bug fixed but it can take years. You can switch to an alternative only to find the replacement also leaks. Many users simply add RAM but that simply makes the time taken to hit the problem longer and it costs money.
RAMMap does seem to offer a workaround that works. I say seem because I have only been testing this use for less than a week. However, the results look promising.
***What is bad about having too much standby RAM and not enough free RAM?***I do not have a technical understanding of the way RAM works. I can only say that it seems logical that where RAM has to be released and a programme is not releasing the tug of war that arises will cause time outs. A time out results in the computer
not responding or freezing.