@ARTICLE{An17-SQJ-CrashInducingCommits,
   AUTHOR       = {Le An and Foutse Khomh and Yann-Ga�l Gu�h�neuc},
   JOURNAL      = {Software Quality Journal (SQJ)},
   TITLE        = {An Empirical Study of Crash-inducing Commits in Mozilla 
      Firefox},
   YEAR         = {2018},
   MONTH        = {June},
   NOTE         = {33 pages.},
   NUMBER       = {2},
   PAGES        = {553--584},
   VOLUME       = {26},
   EDITOR       = {Rachel Harrison},
   KEYWORDS     = {Topic: <b>Code and design smells</b>, Venue: <b>SQJ</b>},
   PUBLISHER    = {Springer},
   URL          = {http://www.ptidej.net/publications/documents/SQJ17a.doc.pdf},
   ABSTRACT     = {Software crashes are dreaded by both software 
      organisations and end-users. Many software organisations have 
      automatic crash reporting tools embedded in their software systems to 
      help quality-assurance teams track and fix crash-related bugs. 
      Previous approaches, which focused on the triaging of crash-types and 
      crash-related bugs, can help software organisations increase their 
      debugging efficiency of crashes. However, these approaches can only 
      be applied after the software systems have been crashing for a 
      certain period of time. To help software organisations detect and fix 
      crash-prone code earlier, we examine the characteristics of commits 
      that lead to crashes, which we call crash-inducing commits, in 
      Mozilla Firefox. We observe that crash-inducing commits are often 
      submitted by developers with less experience and that developers 
      perform more addition and deletion of lines of code in crash-inducing 
      commits but also that they need less effort to fix the bugs caused by 
      these commits. We also characterise commits that would lead to 
      frequent crashes, which impact a large user base, which we call 
      highly impactful crash-inducing commits. Compared to other 
      crash-related bugs, we observe that bugs due to highly impactful 
      crash-inducing commits were less reopened by developers and tend to 
      be fixed by a single commit. We build predictive models to help 
      software organisations detect and fix crash-prone bugs early, when 
      their developers commit code. Our predictive models achieve a 
      precision of 61.2\% and a recall of 94.5\% to predict crash-inducing 
      commits and a precision of 60.9\% and a recall of 91.1\% to predict 
      highly impactful crash-inducing commits. Software organisations could 
      use our models and approach to track and fix crash-prone commits 
      early, before they negatively impact users, thus increasing bug 
      fixing efficiency and user-perceived quality.}
}

{"_id":"tzaoD2RkYNsYbE6cx","bibbaseid":"an-khomh-guhneuc-anempiricalstudyofcrashinducingcommitsinmozillafirefox-2018","downloads":0,"creationDate":"2018-10-22T00:13:29.331Z","title":"An Empirical Study of Crash-inducing Commits in Mozilla Firefox","author_short":["An, L.","Khomh, F.","Gu�h�neuc, Y."],"year":2018,"bibtype":"article","biburl":"http://www.yann-gael.gueheneuc.net/Work/Publications/Biblio/complete-bibliography.bib","bibdata":{"bibtype":"article","type":"article","author":[{"firstnames":["Le"],"propositions":[],"lastnames":["An"],"suffixes":[]},{"firstnames":["Foutse"],"propositions":[],"lastnames":["Khomh"],"suffixes":[]},{"firstnames":["Yann-Ga�l"],"propositions":[],"lastnames":["Gu�h�neuc"],"suffixes":[]}],"journal":"Software Quality Journal (SQJ)","title":"An Empirical Study of Crash-inducing Commits in Mozilla Firefox","year":"2018","month":"June","note":"33 pages.","number":"2","pages":"553–584","volume":"26","editor":[{"firstnames":["Rachel"],"propositions":[],"lastnames":["Harrison"],"suffixes":[]}],"keywords":"Topic: <b>Code and design smells</b>, Venue: <b>SQJ</b>","publisher":"Springer","url":"http://www.ptidej.net/publications/documents/SQJ17a.doc.pdf","abstract":"Software crashes are dreaded by both software organisations and end-users. Many software organisations have automatic crash reporting tools embedded in their software systems to help quality-assurance teams track and fix crash-related bugs. Previous approaches, which focused on the triaging of crash-types and crash-related bugs, can help software organisations increase their debugging efficiency of crashes. However, these approaches can only be applied after the software systems have been crashing for a certain period of time. To help software organisations detect and fix crash-prone code earlier, we examine the characteristics of commits that lead to crashes, which we call crash-inducing commits, in Mozilla Firefox. We observe that crash-inducing commits are often submitted by developers with less experience and that developers perform more addition and deletion of lines of code in crash-inducing commits but also that they need less effort to fix the bugs caused by these commits. We also characterise commits that would lead to frequent crashes, which impact a large user base, which we call highly impactful crash-inducing commits. Compared to other crash-related bugs, we observe that bugs due to highly impactful crash-inducing commits were less reopened by developers and tend to be fixed by a single commit. We build predictive models to help software organisations detect and fix crash-prone bugs early, when their developers commit code. Our predictive models achieve a precision of 61.2% and a recall of 94.5% to predict crash-inducing commits and a precision of 60.9% and a recall of 91.1% to predict highly impactful crash-inducing commits. Software organisations could use our models and approach to track and fix crash-prone commits early, before they negatively impact users, thus increasing bug fixing efficiency and user-perceived quality.","bibtex":"@ARTICLE{An17-SQJ-CrashInducingCommits,\r\n AUTHOR = {Le An and Foutse Khomh and Yann-Ga�l Gu�h�neuc},\r\n JOURNAL = {Software Quality Journal (SQJ)},\r\n TITLE = {An Empirical Study of Crash-inducing Commits in Mozilla \r\n Firefox},\r\n YEAR = {2018},\r\n MONTH = {June},\r\n NOTE = {33 pages.},\r\n NUMBER = {2},\r\n PAGES = {553--584},\r\n VOLUME = {26},\r\n EDITOR = {Rachel Harrison},\r\n KEYWORDS = {Topic: <b>Code and design smells</b>, Venue: <b>SQJ</b>},\r\n PUBLISHER = {Springer},\r\n URL = {http://www.ptidej.net/publications/documents/SQJ17a.doc.pdf},\r\n ABSTRACT = {Software crashes are dreaded by both software \r\n organisations and end-users. Many software organisations have \r\n automatic crash reporting tools embedded in their software systems to \r\n help quality-assurance teams track and fix crash-related bugs. \r\n Previous approaches, which focused on the triaging of crash-types and \r\n crash-related bugs, can help software organisations increase their \r\n debugging efficiency of crashes. However, these approaches can only \r\n be applied after the software systems have been crashing for a \r\n certain period of time. To help software organisations detect and fix \r\n crash-prone code earlier, we examine the characteristics of commits \r\n that lead to crashes, which we call crash-inducing commits, in \r\n Mozilla Firefox. We observe that crash-inducing commits are often \r\n submitted by developers with less experience and that developers \r\n perform more addition and deletion of lines of code in crash-inducing \r\n commits but also that they need less effort to fix the bugs caused by \r\n these commits. We also characterise commits that would lead to \r\n frequent crashes, which impact a large user base, which we call \r\n highly impactful crash-inducing commits. Compared to other \r\n crash-related bugs, we observe that bugs due to highly impactful \r\n crash-inducing commits were less reopened by developers and tend to \r\n be fixed by a single commit. We build predictive models to help \r\n software organisations detect and fix crash-prone bugs early, when \r\n their developers commit code. Our predictive models achieve a \r\n precision of 61.2\\% and a recall of 94.5\\% to predict crash-inducing \r\n commits and a precision of 60.9\\% and a recall of 91.1\\% to predict \r\n highly impactful crash-inducing commits. Software organisations could \r\n use our models and approach to track and fix crash-prone commits \r\n early, before they negatively impact users, thus increasing bug \r\n fixing efficiency and user-perceived quality.}\r\n}\r\n\r\n","author_short":["An, L.","Khomh, F.","Gu�h�neuc, Y."],"editor_short":["Harrison, R."],"key":"An17-SQJ-CrashInducingCommits","id":"An17-SQJ-CrashInducingCommits","bibbaseid":"an-khomh-guhneuc-anempiricalstudyofcrashinducingcommitsinmozillafirefox-2018","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/SQJ17a.doc.pdf"},"keyword":["Topic: <b>Code and design smells</b>","Venue: <b>SQJ</b>"],"metadata":{"authorlinks":{"gu�h�neuc, y":"https://bibbase.org/show?bib=http%3A%2F%2Fwww.yann-gael.gueheneuc.net%2FWork%2FPublications%2FBiblio%2Fcomplete-bibliography.bib&msg=embed"}}},"search_terms":["empirical","study","crash","inducing","commits","mozilla","firefox","an","khomh","gu�h�neuc"],"keywords":["topic: <b>code and design smells</b>","venue: <b>sqj</b>"],"authorIDs":["5a5fb236a39f2c3645000032","5e60e7f0839e59df010000e8","AfJhKcg96muyPdu7S","ahGA65oGDChNYp7Mb"],"dataSources":["8vn5MSGYWB4fAx9Z4"]}