In programming, memory leaks are a common issue, and it occurs when a computer uses memory but does not give it back to the operating system. Experienced programmers have the ability to diagnose a leak based on the symptoms. Some believe every undesired increase in memory usage is a memory leak, but this is not an accurate representation of a leak. Certain leaks only run for a short time and are virtually undetectable.

Memory Leak Consequences

Applications that suffer severe memory leaks will eventually exceed the memory resulting in a severe slowdown or a termination of the application.

How to Protect Code from Memory Leaks?

Preventing memory leaks in the first place is more convenient than trying to locate the leak later. To do this, you can use defensive programming techniques such as smart pointers for C++.  A smart pointer is safer than a raw pointer because it provides augmented behavior that raw pointers do not have. This includes garbage collection and checking for nulls.

If you are going to use a raw pointer, avoid operations that are dangerous for specific contexts. This means pointer arithmetic and pointer copying. Smart pointers use a reference count for the object being referred to. Once the reference count reaches zero, the excess goes into garbage collection. The most commonly used smart pointer is shared_ptr from the TR1 extensions of the C++ standard library.

Static Analysis

The second approach to memory leaks is referred to as static analysis and attempts to detect errors in your source-code. CodeSonar is one of the effective tools for detection. It provides checkers for the Power of Ten coding rules, and it is especially competent at procedural analysis. However, some might find it lagging for bigger code bases.

How to Handle a Memory Leak

For some memory leaks, the only solution is to read through the code to find and correct the error. Another one of the common approaches to C++ is to use RAII, which an acronym for Resource Acquisition Is Initialization. This approach means associating scoped objects using the acquired resources, which automatically releases the resources when the objects are no longer within scope. RAII has the advantage of knowing when objects exist and when they do not. This gives it a distinct advantage over garbage collection. Regardless, RAII is not always recommended because some situations require ordinary pointers to manage raw memory and increase performance. Use it with caution.

The Most Serious Leaks

Urgency of a leak depends on the situation, and where the leak has occurred in the operating system. Additionally, it becomes more urgent if the leak occurs where the memory is limited such as in embedded systems and portable devices.

To protect code from memory leaks, people have to stay vigilant and avoid codes that could result in a leak. Memory leaks continue until someone turns the system off, which makes the memory available again, but the slow process of a leak can eventually prejudice a machine that normally runs correctly.

Related:

The Five Principles of Performance

In Demand IT Skills

Every programming language has a mechanism to allow the programmer to create variables which hold custom data entered in by either the coder themselves or by the user of the application.

Regardless of whether you’re new to programming or not, you will have used variables and you should understand that in javascript they can hold any value such as a number or a string of text.

There is also another type of variable called an Array. Now, depending on who you talk to, some will say an array is actually an object, while others say it is a variable. Neither one is wrong but for the sake of simplicity we’ll refer to it as a variable.

Now, arrays are special because they can hold multiple values as opposed to standard variables which can only hold a single value at one time. If you can, try and imagine that your computer’s memory is made up of thousands of little boxes, and each of those boxes has an address which javascript will use to retrieve the array values when needed.

Below are two pdf's which discuss and outline the Java Message Service, JMS, tutorial.

One Hour Java Messaging Service Tutorial
Advanced One Hour Java Messaging Service Tutorial

 

Structure Rule Language

To aid in the ease of rule authoring, Blaze Software, now Fair Isaac, created the proprietary Structure Rule Language (SRL), an object-oriented programming language designed to enable those with little or no background in software development to pen rules. Although the capabilities of this language are far too extensive to detail in this article, we can examine the basic rule syntax.

Rules in the SRL take the following form:

rule RuleName [at | priority M] is