Demo Data from VLDB 2026 / reviewers in the wild / expert
Hyeongi Hong
dblp:412/1865
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2025
0009-0000-3372-5583ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Debugging and program repair · 75% Program analysis · 25% | |
| Network and information security
1 paper |
Web and mobile security · 100% |
Topics — the 5 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Debugging and program repair
automated program repair |
0.9 | 1 | 2025 | Proactive Debugging of Memory Leakage Bugs in Single Page Web Applications · IEEE Trans. Software Eng. 2025 |
Debugging and program repair
fault localization |
0.9 | 1 | 2025 | Proactive Debugging of Memory Leakage Bugs in Single Page Web Applications · IEEE Trans. Software Eng. 2025 |
Program analysis › error detection
memory leak detection |
0.9 | 1 | 2025 | Proactive Debugging of Memory Leakage Bugs in Single Page Web Applications · IEEE Trans. Software Eng. 2025 |
Debugging and program repair › automated program repair
memory leak repair |
0.9 | 1 | 2025 | Proactive Debugging of Memory Leakage Bugs in Single Page Web Applications · IEEE Trans. Software Eng. 2025 |
Web and mobile security
web application security |
0.3 | 1 | 2025 | Proactive Debugging of Memory Leakage Bugs in Single Page Web Applications · IEEE Trans. Software Eng. 2025 |
Methods — techniques the papers use, named apart from their topics
pattern-based program repair · 1.7large language model · 1.7
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Proactive Debugging of Memory Leakage Bugs in Single Page Web ApplicationsabstractDeveloping modern web applications often relies on web-based application frameworks such as React, Vue.js, and Angular. Although the frameworks accelerate the development of web applications with several useful and predefined components, they are inevitably vulnerable to unmanaged memory consumption as the frameworks often produce monolithic web pages, socalled, Single Page Applications (SPAs), in which no page refresh actions are made during navigation.Web applications can be alive for hours and days with behavior loops, in such cases, even a single memory leak in an SPA can cause performance degradation on the client side. However, recent debugging techniques for web applications focus on memory leak detection, which requires manual tasks and produces imprecise results, rather than proactively repairing memory leaks.We propose LEAKPAIR, a technique to proactively repair memory leaks in SPAs rather than following a classical and reactive debugging process. Given the insight that memory leaks are mostly non-functional bugs and fixing them might not change the behavior of an application, the technique is designed to proactively generate patches to fix memory leaks, without leak detection, which is often heavy and tedious. Thus, the proactive technique can significantly reduce the time and effort necessary to fix the memory leaks. To generate effective patches, LEAKPAIR follows the idea of pattern-based program repair since the automated repair strategy shows successful results in many recent studies. We extensively evaluate the technique on 60 open-source projects without using explicit leak detection. The patches generated by our technique are also submitted to the projects as pull requests (PRs). The results of PRs show that LEAKPAIR can generate effective patches to reduce memory consumption that are acceptable to developers. In addition, we execute the test suites given by the projects after applying the patches, and it turns out that the patches do not cause any functionality breakage; this might imply that LEAKPAIR can generate non-intrusive patches for memory leaks. Furthermore, we compare the performance of LEAKPAIR with that of GPT-4 as recent studies show that large language models are successful with program repair tasks. Our results show that our technique outperforms the language model. Arooba Shahoor, Satbek Abdyldayev, Hyeongi Hong, Jooyong Yi, Dongsun Kim 0001 |
IEEE Trans. Software Eng. | 3 |