2016
DOI: 10.1002/spe.2406
|View full text |Cite
|
Sign up to set email alerts
|

LeakSpot: detection and diagnosis of memory leaks in JavaScript applications

Abstract: Summary The migration of application logic to the client side of modern web applications and the use of JavaScript as the main language for client‐side development have made memory leaks in JavaScript an issue for web applications. Client‐side web applications communicate with the server asynchronously, remaining on the same web page during their lifetime. Thus, even minor memory leaks can eventually lead to excessive memory usage, negatively affecting user‐perceived response time and possibly causing page cra… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
7
0

Year Published

2018
2018
2024
2024

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 11 publications
(7 citation statements)
references
References 29 publications
0
7
0
Order By: Relevance
“…Based on the staleness measure of allocated objects, Rudaf et al proposed "LeakSpot" for detecting memory leaks in web applications [13]. It locates JavaScript allocation and reference sites that produce and retain increasing numbers of objects over time and uses staleness as a heuristic to identify memory leaks.…”
Section: Related Workmentioning
confidence: 99%
“…Based on the staleness measure of allocated objects, Rudaf et al proposed "LeakSpot" for detecting memory leaks in web applications [13]. It locates JavaScript allocation and reference sites that produce and retain increasing numbers of objects over time and uses staleness as a heuristic to identify memory leaks.…”
Section: Related Workmentioning
confidence: 99%
“…Based on the staleness measure of allocated objects, Rudaf et al proposed "LeakSpot" for detecting memory leaks in web applications [9]. It locates JavaScript allocation and reference sites that produce and retain increasing numbers of objects over time and uses staleness as a heuristic to identify memory leaks.…”
Section: Related Workmentioning
confidence: 99%
“…Web application memory leak detectors: BL automatically debugs memory leaks in modern web applications; past work in this space is ineffective, out of date, or not sufficiently general. LeakSpot locates JavaScript allocation and reference sites that produce and retain increasing numbers of objects over time, and uses staleness as a heuristic to refine its output [52]. On real web applications, LeakSpot typically reports over 50 different allocation and reference sites that developers must manually inspect to identify and diagnose memory leaks.…”
Section: Related Workmentioning
confidence: 99%
“…The reason is that existing memory leak detection techniques are ineffective in the browser: leaks in web applications are fundamentally different from leaks in traditional C, C++, and Java programs. Staleness-based techniques assume leaked memory is rarely touched [8,25,48,52,74], but web applications regularly interact with leaked state (e.g., via event listeners). Growthbased techniques assume that leaked objects are uniquely owned or that leaked objects form strongly connected components in the heap graph [41,74].…”
Section: Introductionmentioning
confidence: 99%