Context- and path-sensitive memory leak detection

Xie, Yichen; Aiken, Alex

doi:10.1145/1081706.1081728

Cited by 80 publications

(57 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…After we identify these procedures, we could identify and fix the leaks of m in the procedure which calls an alloc procedure of m but itself is not an alloc procedure of m. This is based on Xie and Aiken's rule [8]: any allocation in a procedure P that does not escape from P is leaked if it is not deallocated in P . In our example, we should check and fix leaks in the procedure check_records.…”

Section: B Basic Ideamentioning

confidence: 99%

“…The main line of static approaches is to detect leaks [7,8,29,9,10,13,11,12,30]. Most detection approaches report only the locations where the leaked memory is allocated.…”

Section: Related Workmentioning

confidence: 99%

“…First, dealing with memory leak is an important problem in software development. While many approaches [7,8,9,10,11,12,13] have been proposed to detect memory leaks, it is still difficult to fix a [14,15]. Second, memory leaks cannot be easily handled by general bug-fixing approaches, as we cannot easily specify the condition of "no leak" as an assertion or a test case.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Safe Memory-Leak Fixing for C Programs

Gao

Xiong

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

View full text Add to dashboard Cite

Abstract-Automatic bug fixing has become a promising direction for reducing manual effort in debugging. However, general approaches to automatic bug fixing may face some fundamental difficulties. In this paper, we argue that automatic fixing of specific types of bugs can be a useful complement.This paper reports our first attempt towards automatically fixing memory leaks in C programs. Our approach generates only safe fixes, which are guaranteed not to interrupt normal execution of the program. To design such an approach, we have to deal with several challenging problems such as inter-procedural leaks, global variables, loops, and leaks from multiple allocations. We propose solutions to all the problems and integrate the solutions into a coherent approach.We implemented our inter-procedural memory leak fixing into a tool named LeakF ix and evaluated LeakF ix on 15 programs with 522k lines of code. Our evaluation shows that LeakF ix is able to successfully fix a substantial number of memory leaks, and LeakF ix is scalable for large applications.

show abstract

Section: B Basic Ideamentioning

confidence: 99%

“…The main line of static approaches is to detect leaks [7,8,29,9,10,13,11,12,30]. Most detection approaches report only the locations where the leaked memory is allocated.…”

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Safe Memory-Leak Fixing for C Programs

Gao

Xiong

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

View full text Add to dashboard Cite

show abstract

“…The same limitation applies to the techniques described in [12,9]. Similarly, the static analyses described in [6,26] aim at detecting leaks caused by objects not reachable from program variables. Therefore they cannot detect the kind of leaks we aim at with our analysis.…”

Section: Related Workmentioning

confidence: 99%

Memory Leaks Detection in Java by Bi-abductive Inference

Distefano

Filipović

2010

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…Generally, memory leak detection methods can be divided into static detection and dynamic detection. Static detection methods, such as context-sensitive, path-sensitive and flow-sensitive [7]- [10], are usually applied to detect memory leaks. But static detection could not reflect the run-time heap information accurately.…”

Section: Introductionmentioning

confidence: 99%

A Detection and Measurement Approach for Memory Leaked Objects in Java Programs

Qiao

Jiang

Liu

2015

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYMemory leak occurs when useless objects cannot be released for a long time during program execution. Memory leaked objects may cause memory overflow, system performance degradation and even cause the system to crash when they become serious. This paper presents a dynamic approach for detecting and measuring memory leaked objects in Java programs. First, our approach tracks the program by JDI and records heap information to find out the potentially leaked objects. Second, we present memory leaking confidence to measure the influence of these objects on the program. Finally, we select three open-source programs to evaluate the efficiency of our approach. Furthermore, we choose ten programs from DaCapo 9.12 benchmark suite to reveal the time overhead of our approach. The experimental results show that our approach is able to detect and measure memory leaked objects efficiently. key words: memory leak, heap information, leaked objects, memory leaking confidence

show abstract

Context- and path-sensitive memory leak detection

Cited by 80 publications

References 15 publications

Safe Memory-Leak Fixing for C Programs

Safe Memory-Leak Fixing for C Programs

Memory Leaks Detection in Java by Bi-abductive Inference

A Detection and Measurement Approach for Memory Leaked Objects in Java Programs

Contact Info

Product

Resources

About