The DOI matches its Crossref record; 15 of the 15 references it cites were found in a registry or an index.
An approach to detecting duplicate bug reports using natural language and execution information
Abstract
An open source project typically maintains an open bug repository so that bug reports from all over the world can be gathered. When a new bug report is submitted to the repository, a person, called a triager, examines whether it is a duplicate of an existing bug report. If it is, the triager marks it as DUPLICATE and the bug report is removed from consideration for further work. In the literature, there are approaches exploiting only natural language information to detect duplicate bug reports. In this paper we present a new approach that further involves execution information. In our approach, when a new bug report arrives, its natural language information and execution information are compared with those of the existing bug reports. Then, a small number of existing bug reports are suggested to the triager as the most similar bug reports to the new bug report. Finally, the triager examines the suggested bug reports to determine whether the new bug report duplicates an existing bug report. We calibrated our approach on a subset of the Eclipse bug repository and evaluated our approach on a subset of the Firefox bug repository. The experimental results show that our approach can detect 67%-93% of duplicate bug reports in the Firefox bug repository, compared to 43%-72% using natural language information alone.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Foundations of statistical natural language processing
Manning, C. D., & Schütze, H. (1999) · Cited by 9,816
Two case studies of open source software development: Apache and Mozilla
Mockus, A., Fielding, R. T., & Herbsleb, J. D. (2002) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/567793.567795 · Cited by 1,685
Anvik, J., Hiew, L., & Murphy, G. C. (2006) · Proceedings of the 28th international conference on Software engineering · doi:10.1145/1134285.1134336 · Cited by 924
Self-citationDetection of Duplicate Defect Reports Using Natural Language Processing
Runeson, P., Alexandersson, M., & Nyholm, O. (2007) · 29th International Conference on Software Engineering (ICSE'07) · doi:10.1109/icse.2007.32 · Cited by 523
Bug isolation via remote program sampling
Liblit, B., Aiken, A., Zheng, A. X., & Jordan, M. I. (2003) · ACM SIGPLAN Notices · doi:10.1145/780822.781148 · Cited by 504
A critical analysis of vector space model for information retrieval
Raghavan, V. V., & Wong, S. K. M. (1986) · Journal of the American Society for Information Science · doi:10.1002/asi.4630370502 · Cited by 315
Automated support for classifying software failure reports
Podgurski, A., Leon, D., Francis, P., Masri, W., & Minch, M. (2003) · Cited by 314
Coping with an open bug repository
Anvik, J., Hiew, L., & Murphy, G. C. (2005) · Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange - eclipse '05 · doi:10.1145/1117696.1117704 · Cited by 252
Self-citationBug isolation via remote program sampling
Liblit, B., Aiken, A., Zheng, A. X., & Jordan, M. I. (2003) · Proceedings of the ACM SIGPLAN 2003 conference on Programming language design and implementation · doi:10.1145/781131.781148 · Cited by 241
A Linguistic Analysis of How People Describe Software Problems
Ko, A. J., Myers, B. A., & Chau, D. H. (2006) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2006.3 · Cited by 179
An approach to classify software maintenance requests
Lucca, G. A. D., Penta, M. D., & Gradara, S. (2003) · International Conference on Software Maintenance · doi:10.1109/icsm.2002.1167756 · Cited by 121
A Technique for Enabling and Supporting Debugging of Field Failures
Clause, J., & Orso, A. (2007) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2007.10 · Cited by 100
Profiling deployed software: assessing strategies and testing opportunities
Elbaum, S. G., & Diep, M. M. (2005) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2005.50 · Cited by 91
Tree-Based Methods for Classifying Software Failures
Francis, P., Leon, D., Minch, M., & Podgurski, A. (2005) · Proceedings/Proceedings - International Symposium on Software Reliability Engineering · doi:10.1109/issre.2004.43 · Cited by 81
Bug report networks: varieties, strategies, and impacts in a F/OSS development community
Sandusky, R. J. (2004) · International Conference on Mining Software Repositories (MSR) · doi:10.1049/ic:20040481 · Cited by 78
Cited by
Bettenburg, N., Just, S., Schröter, A., Weiss, C., Premraj, R., & Zimmermann, T. (2008) · Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering · doi:10.1145/1453101.1453146 · Cited by 617
Zhou, J., Zhang, H., & Lo, D. (2012) · 2012 34th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2012.6227210 · Cited by 507
Improving bug triage with bug tossing graphs
Jeong, G., Kim, S., & Zimmermann, T. (2009) · Proceedings of the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering · doi:10.1145/1595696.1595715 · Cited by 455
ReLink: recovering links between bugs and changes
Wu, R., Zhang, H., Kim, S., & Cheung, S.-C. (2011) · Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering · doi:10.1145/2025113.2025120 · Cited by 412
Zhou, J. H., Zhang, H., & Lo, D. (2012) · doi:10.5555/2337223.2337226 · Cited by 372
Metadata
- Authors
- Wang, X., Zhang, L., Xie, T., Anvik, J., & Sun, J.
- Venue
- Proceedings of the 13th international conference on Software engineering - ICSE '08
- Publisher
- ACM Press
- Published
- 2008
- Pages
- 461
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W2156833313
- Cited by
- 539
- References
- 15
- FWCI
- 19.41
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.