Are you tired of spending countless hours devoted to fixing memory faults? Do you find yourself constantly being bogged down in programs that leak memory, violate memory bounds, use uninitialized data, and devote an excessive amount of run time to memory management? Use this article to help you conquer these pesky memory defects.

Memory leaks and memory corruptions are problems that can be easily introduced in code written in C or C++ and generally in any programming language that does not have a garbage collector built in, causing system crashes and sometimes, even worse, unexpected behavior, creating bugs that are difficult to be detected.

For most users, Firefox doesn't use an abnormally large amount of memory. For others, however, Firefox's memory consumption is a major problem (Especilaly for people using old computers with limited memory resources), in same cases memory usage in Firefox is due some to other sources, like number of plug-ins, themes and extensions.

The CPU and the GPU share access to some pages of memory. New Linux code helps the kernel keep track of memory holding data for the GPU.

The Linux memory management code does its best to ensure that memory will always be available when some part of the system needs it. That effort notwithstanding, it is still possible for a system to reach a point where no memory is available.

First, I have to say that this is not a generic memory manager. It is specific to my application. It may be possible to adapt it to other applications, but the key word here is 'adapt'. However, it will hopefully give anyone who is considering doing their own memory management some food for thought.

Phase change memory (PCM) - an emerging non-volatile technology pioneered by Intel, Numonyx, Samsung and others - could turn out to be a low-cost, more reliable, faster, and just plain better alternative to flash memory

Sometimes Firefox can become a real memory hog, especially if you keep it running for hours and have many tabs opened. In order to make Firefox a little more responsive and save some RAM memory, here are three tweaks I bumped into over time. Notice that most of these tips only free up some memory at the expense of (usually) loading speed for web pages.

Article about vmstat tool, to check the memory status in a Linux system, explaining the terms that vmstat uses, and also how to solve some memory problems, (only some hints)