Browse Prior Art Database

Automatic Memory Leak Tracker Disclosure Number: IPCOM000234082D
Publication Date: 2014-Jan-10
Document File: 2 page(s) / 142K

Publishing Venue

The Prior Art Database


Disclosed is a system for an automatic memory leak tracker for software systems.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

Automatic Memory Leak Tracker

Memory Leak Tracking in software systems is difficult. Often, neither development nor testing processes can catch the memory leaks. Memory leaks accumulate over time and create a problem, which can go undetected by reviews or tests. The scope of the memory leak is not always known or is unmarked, and the properties are not readily available (e.g., when to free the piece of memory that is allocated). Unless a single leak is very large, it might repeatedly execute the same faulty code. The leak might not be fatal right away, but require a higher level of cleanup. In addition, if a leak is detected, it is often difficult to determine the cause of the leak . Low-level languages are more vulnerable and do not have an embedded method of leak detection.

With existing methods for memory leak detection , it is very difficult to detect a leak
or categorize a problem as a leak. Detection requires a lot of observation over time. Manual intervention is required to conclude the leaks, and the testing often produces false positives. In addition, the tools are not seamless, which causes performance


The solution is a system for an automatic memory leak tracker . The components and process for implementing the system follow:

1. Startup of software system

2. Run the functionalities to be tested and track each allocation and free associate with exact call sequence derived from stack traceback

A. Exception 1: Do not track specific markers. Allocation is done, but free

would be done by higher memory pool where the allocation might come from a sub memory pool and parent would be freeing it .

B. Exception 2: Do not track tracking object allocations that are the embedded in the tool

3. Stop software system

4. Dump all the elements which are not freed, but are allocated with offender exact stack walk-back information associated are the leaks (unless marked as do not track)

Memory Leak Tracking is built on pairs of the very same object; that is used to t...