Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

MLK.MUST

Memory leak

The program did not release previously allocated memory and a reference to dynamic memory is lost at this point.

Vulnerability and risk

Memory leaks cause the application to consume additional memory. This reduces the amount of memory available to other applications and eventually causes the operating system to start paging, slowing the system down. In critical cases, the application will reach overall memory limits, which may result in application crashes.

Example 1

1  class A{
2     void foo();
3  };
4   void A::foo()
5   {
6     int *ptr = new int;
7     *ptr = 25;
8     ptr = new int;
9     *ptr = 35;
10  }

Klocwork produces a memory leak report for line 8, indicating that the dynamic memory stored in 'ptr' allocated through the function 'new' at line 6 is lost at line 8. In the above example, another memory leak is reported for line 10: the dynamic memory stored in 'ptr' allocated through the function 'new' at line 8 is lost at line 10.