Which Crashes Should I Fix First?: Predicting Top Crashes at an Early Stage to Prioritize Debugging Efforts
Issue No. 03 - May/June (2011 vol. 37)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/TSE.2011.20
Dongsun Kim , Sogang University, Seoul
Xinming Wang , The Hong Kong University of Science and Technology, Hong Kong
Sunghun Kim , The Hong Kong University of Science and Technology, Hong Kong
Andreas Zeller , Saarland University, Saarbrücken
S.C. Cheung , The Hong Kong University of Science and Technology, Hong Kong
Sooyong Park , Sogang University, Seoul
Many popular software systems automatically report failures back to the vendors, allowing developers to focus on the most pressing problems. However, it takes a certain period of time to assess which failures occur most frequently. In an empirical investigation of the Firefox and Thunderbird crash report databases, we found that only 10 to 20 crashes account for the large majority of crash reports; predicting these “top crashes” thus could dramatically increase software quality. By training a machine learner on the features of top crashes of past releases, we can effectively predict the top crashes well before a new release. This allows for quick resolution of the most important crashes, leading to improved user experience and better allocation of maintenance efforts.
Top crash, machine learning, crash reports, social network analysis, data mining.
S. Kim, S. Park, X. Wang, A. Zeller, S. Cheung and D. Kim, "Which Crashes Should I Fix First?: Predicting Top Crashes at an Early Stage to Prioritize Debugging Efforts," in IEEE Transactions on Software Engineering, vol. 37, no. , pp. 430-447, 2011.