2018
DOI: 10.1145/3296979.3192376
|View full text |Cite
|
Sign up to set email alerts
|

BLeak: automatically debugging memory leaks in web applications

Abstract: Despite the presence of garbage collection in managed languages like JavaScript, memory leaks remain a serious problem. In the context of web applications, these leaks are especially pervasive and difficult to debug. Web application memory leaks can take many forms, including failing to dispose of unneeded event listeners, repeatedly injecting iframes and CSS files, and failing to call cleanup routines in third-party libraries. Leaks degrade responsiveness by increasing GC frequency and overhead, and can even … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 14 publications
0
3
0
Order By: Relevance
“…One typical way for memory leak diagnosis is to investigate the memory occupations and growths of data structures, for example, Ref. [6,7,19,20]. Another is to watch the object lifetime information, such as the object staleness, for example, Ref.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…One typical way for memory leak diagnosis is to investigate the memory occupations and growths of data structures, for example, Ref. [6,7,19,20]. Another is to watch the object lifetime information, such as the object staleness, for example, Ref.…”
Section: Related Workmentioning
confidence: 99%
“…Despite great efforts having already been devoted to the root cause diagnosis of memory bloat in a programme execution with bloat phenomena observed, for example, Ref. [2,[4][5][6][7][8][9], challenges still remain regarding how to first find those memory bloated programme executions.…”
Section: Introductionmentioning
confidence: 99%
“…BLeak [37] automatically debugs the memory leak problem which increases garbage collection frequency and overhead, further degrading responsiveness. Faddegon et al [17] presented a computation tree generaration method that requires only a simple tracing library, for debugging any Haskell programs.…”
Section: Related Workmentioning
confidence: 99%