View Single Post
Old 10. Apr 2015, 01:03 PM   #33 (permalink)
Senior Member
Join Date: Jul 2010
Location: New Zealand
Posts: 1,741

Originally Posted by MidnightCowboy View Post
Could this be the result of a memory "leak"? I remembered this issue from last year, maybe there are others?
It might well be because they are very common. Most are usually of limited impact and nobody notices a problem. Some exhaust Windows memory resources. But even if it is a memory leak that doesn't help to resolve it because the developer needs to change the program. That's why I would focus on the problem of which program is using more memory rather than trying to identify if a memory "leak" is the cause.

A memory leak simply means that a program is not releasing memory that it no longer needs. They are hard to identify because to us users it will usually look no different than a program that actually needs the memory it is using. We have a current example in the memory usage of the program Glasswire. This week we have been discussing that issue in another forum thread. Glasswire has an increasing demand for memory over time because it stores its monitoring data in memory. It might have a memory leak as well but how would we know unless we have some baseline to compare it with. Unless we know what memory usage should be then it is difficult to distinguish an increase in memory used due to a leak versus data collecting in memory.

The Wikipedia article on memory leaks explains the issues very well: consequences and effects, and other reasons why memory is being consumed.

The first half of this Microsoft article Preventing Memory Leaks in Windows Applications mentions how to use Task Manager to baseline the memory profile for a program. The average user only needs to monitor the commit size because the other measures like handles and threads are generally going to be harder to interpret/understand and more useful to programmers.
Better to light a candle ... than to curse the darkness.
Remah is offline   Reply With Quote