mlsanityData to 7 Oct 2026

Bug Characterization in Machine Learning-based Systems

arXiv 2307.14512 ↗First posted 26 Jul 2023cs.SE cs.LGcited by 10

Not on the map. Why?

Abstract (arXiv)

Rapid growth of applying Machine Learning (ML) in different domains, especially in safety-critical areas, increases the need for reliable ML components, i.e., a software component operating based on ML. Understanding the bugs characteristics and maintenance challenges in ML-based systems can help developers of these systems to identify where to focus maintenance and testing efforts, by giving insights into the most error-prone components, most common bugs, etc. In this paper, we investigate the characteristics of bugs in ML-based software systems and the difference between ML and non-ML bugs from the maintenance viewpoint. We extracted 447,948 GitHub repositories that used one of the three most popular ML frameworks, i.e., TensorFlow, Keras, and PyTorch. After multiple filtering steps, we select the top 300 repositories with the highest number of closed issues. We manually investigate the extracted repositories to exclude non-ML-based systems. Our investigation involved a manual inspection of 386 sampled reported issues in the identified ML-based systems to indicate whether they affect ML components or not. Our analysis shows that nearly half of the real issues reported in ML-based systems are ML bugs, indicating that ML components are more error-prone than non-ML components. Next, we thoroughly examined 109 identified ML bugs to identify their root causes, symptoms, and calculate their required fixing time. The results also revealed that ML bugs have significantly different characteristics compared to non-ML bugs, in terms of the complexity of bug-fixing (number of commits, changed files, and changed lines of code). Based on our results, fixing ML bugs are more costly and ML components are more error-prone, compared to non-ML bugs and non-ML components respectively. Hence, paying a significant attention to the reliability of the ML components is crucial in ML-based systems.

Key facts. Cited by 10 papers in the map (data through 7 Oct 2026). Builds on 21 of its 107 references that are in the map. First posted on arXiv 26 Jul 2023.

Builds on

21 of 107 references.

References · 21

  1. 2019PyTorch: An Imperative Style, High-Performance Deep Learning Librarycited by 20,160
  2. 2014Caffe: Convolutional Architecture for Fast Feature Embeddingcited by 287
  3. 2019Machine Learning Testing: Survey, Landscapes and Horizonscited by 213
  4. 2015MXNet: A Flexible and Efficient Machine Learning Library for Heterogeneous Distributed Systemscited by 195
  5. 2019Taxonomy of Real Faults in Deep Learning Systemscited by 90
  6. 2021Software Engineering for AI-Based Systems: A Surveycited by 68
  7. 2019A Comprehensive Study on Deep Learning Bug Characteristicscited by 65
  8. 2021Model Complexity of Deep Learning: A Surveycited by 64
  9. 2021DeepLocalize: Fault Localization for Deep Neural Networkscited by 37
  10. 2020Repairing Deep Neural Networks: Fix Patterns and Challengescited by 33
  11. 2021Silent Bugs in Deep Learning Frameworks: An Empirical Study of Keras and TensorFlowcited by 25
  12. 2021DeepDiagnosis: Automatically Diagnosing Faults and Recommending Actionable Fixes in Deep Learning Programscited by 19
9 more
  1. 2021Faults in Deep Reinforcement Learning Programs: A Taxonomy and A Detection Approachcited by 18
  2. 2022Bugs in Machine Learning-based Systems: A Faultload Benchmarkcited by 15
  3. 2021Understanding Performance Problems in Deep Learning Systemscited by 12
  4. 2021Automatic Fault Detection for Deep Learning Programs Using Graph Transformationscited by 9
  5. 2022On Reporting Performance and Accuracy Bugs for Deep Learning Frameworks: An Exploratory Study from GitHubcited by 6
  6. 2021The challenge of reproducible ML: an empirical study on the impact of bugscited by 3
  7. 2017What is the Connection Between Issues, Bugs, and Enhancements? (Lessons Learned from 800+ Software Projects)cited by 2
  8. 2021Same File, Different Changes: The Potential of Meta-Maintenance on GitHubcited by 1
  9. 2022Revisiting reopened bugs in open source software systemscited by 1

Built on by

Cited by year (2026 to 7 Oct)

Citing papers per year: 2023: 1; 2024: 2; 2025: 2; 2026: 5.

10 papers.