Open Access   Article Go Back

Clustering The Duplicate Open Crash Reports Based on Call Stack Traces of Crash Reports

Pushpalatha M N1 , runalini M2

Section:Research Paper, Product Type: Journal Paper
Volume-6 , Issue-9 , Page no. 207-210, Sep-2018

CrossRef-DOI:   https://doi.org/10.26438/ijcse/v6i9.207210

Online published on Sep 30, 2018

Copyright © Pushpalatha M N, Mrunalini M . This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

View this paper at   Google Scholar | DPI Digital Library

XML View
PDF Download

How to Cite this Paper

  • IEEE Citation
  • MLA Citation
  • APA Citation
  • BibTex Citation
  • RIS Citation

IEEE Style Citation: Pushpalatha M N, Mrunalini M, “Clustering The Duplicate Open Crash Reports Based on Call Stack Traces of Crash Reports,” International Journal of Computer Sciences and Engineering, Vol.6, Issue.9, pp.207-210, 2018.

MLA Style Citation: Pushpalatha M N, Mrunalini M "Clustering The Duplicate Open Crash Reports Based on Call Stack Traces of Crash Reports." International Journal of Computer Sciences and Engineering 6.9 (2018): 207-210.

APA Style Citation: Pushpalatha M N, Mrunalini M, (2018). Clustering The Duplicate Open Crash Reports Based on Call Stack Traces of Crash Reports. International Journal of Computer Sciences and Engineering, 6(9), 207-210.

BibTex Style Citation:
@article{N_2018,
author = {Pushpalatha M N, Mrunalini M},
title = {Clustering The Duplicate Open Crash Reports Based on Call Stack Traces of Crash Reports},
journal = {International Journal of Computer Sciences and Engineering},
issue_date = {9 2018},
volume = {6},
Issue = {9},
month = {9},
year = {2018},
issn = {2347-2693},
pages = {207-210},
url = {https://www.ijcseonline.org/full_paper_view.php?paper_id=2846},
doi = {https://doi.org/10.26438/ijcse/v6i9.207210}
publisher = {IJCSE, Indore, INDIA},
}

RIS Style Citation:
TY - JOUR
DO = {https://doi.org/10.26438/ijcse/v6i9.207210}
UR - https://www.ijcseonline.org/full_paper_view.php?paper_id=2846
TI - Clustering The Duplicate Open Crash Reports Based on Call Stack Traces of Crash Reports
T2 - International Journal of Computer Sciences and Engineering
AU - Pushpalatha M N, Mrunalini M
PY - 2018
DA - 2018/09/30
PB - IJCSE, Indore, INDIA
SP - 207-210
IS - 9
VL - 6
SN - 2347-2693
ER -

VIEWS PDF XML
497 373 downloads 282 downloads
  
  
           

Abstract

A computer program such as software application that stops functioning properly is called software crash. Software crash is tedious problem in software development environment. Upon user permission, the crash report which contains the stack traces is sent to the developer or vendor. Software development team receives hundreds of crash reports from many deployment sites. There are many duplicate crash reports are generated, because many users submit the crash reports for the same problem. For analysing each crash reports, it may take more time. This motivates, to present the solution to analyse the crash reports and cluster the duplicate crash reports based on call stack similarities and store them into unique bucket, so that development resources can be optimized. In this paper, clustering the duplicate crash report of open source is proposed based on the similar information in the call stack. Hierarchical clustering technique is used to cluster the duplicate crash reports into unique bucket. Mozilla and Firefox open source crash reports are used for experiment and performance evaluation is done using purity determined the purity of clusters up to 80%. This method helps to increase the efficiency and reduce the number of developers along with an improved time to fix the bug.

Key-Words / Index Term

Crash reports, clustering technique

References

[1] Asha Ramaraddi Belahunashi, Pushpalatha M N,” A Survey on analysing the crash reports of software applications”, International Research Journal of Engineering and Technology , Volume 4, Issue 6, pp.1014-1017, June 2017.
[2] Divya R S, Pushpalatha M N, “Software CrashLocator: Locating the Faulty Functions by Analyzing the Crash Stack Information in Crash Reports”, International Journal of Advanced Engineering, Management and Science (IJAEMS), Vol-2, Issue-5, pp.269-273, May- 2016
[3] Rongxin Wu, Hongyu Zhang, Shing-Chi Cheung, and Sunghun Kim, “CrashLocator: Locating Crashing Faults Based on Crash Stacks”, ISSTA 2014 Proceedings of the 2014 International Symposium on Software Testing and Analysis, Pages 2014-214, 2014


[4] Yingnong Dang, Rongxin Wu, Hongyu Zhang, Dongmei Zhang, and Peter Nobel, “Rebucket: a method for clustering duplicate crash reports based on call stack similarity”. In Proceedings of the 34th International Conference on Software Engineering, pages 1084– 1093. IEEE Press, 2012.
[5] P. Runeson, M. Alexandersson, and O. Nyholm, “Detection of Duplicate Defect Reports Using Natural Language Processing”, in Proc. ICSE 2007, Minneapolis,USA, pp. 499-510, May 2007.
[6] X. Wang, L. Zhang, T. Xie, J. Anvik, and J. Sun, "An approach to detecting duplicate bug reports using natural language and execution information", in Proc. ICSE’08, Leipzig, Germany, pp. 461-470, 2008
[7] D. Kim, X. Wang, S. Kim, A. Zeller, S. Cheung, and S. Park, “Which crashes should i fix first? Predicting top crashes at an early stage to prioritize debugging efforts”, IEEE Transactions on Software Engineering, pp. 430-447, 2011