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.RET.MIGHT

Memory leak possible

The MLK.RET.MIGHT issue is reported when memory may be allocated and returned from a function, depending on certain conditions, but is not assigned to any variable. The allocated 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  void* alloc_data(void* pool)
2  {
3    if (pool) {
4       return pool_alloc(pool, 10);
5    } else {
6       return malloc(10);
7    }
8  }
9
10  void foo(void* pool)
11  {
12    alloc_data(pool);
13  }

Klocwork produces a memory leak report indicating that dynamic memory which might be allocated through function 'alloc_data' is lost at line 12.