Actor concurrency bugs: a comprehensive study on symptoms, root causes, API usages, and differences
- 13 November 2020
- journal article
- research article
- Published by Association for Computing Machinery (ACM) in Proceedings of the ACM on Programming Languages
- Vol. 4 (OOPSLA), 1-32
- https://doi.org/10.1145/3428282
Abstract
Actor concurrency is becoming increasingly important in the development of real-world software systems. Although actor concurrency may be less susceptible to some multithreaded concurrency bugs, such as low-level data races and deadlocks, it comes with its own bugs that may be different. However, the fundamental characteristics of actor concurrency bugs, including their symptoms, root causes, API usages, examples, and differences when they come from different sources are still largely unknown. Actor software development can significantly benefit from a comprehensive qualitative and quantitative understanding of these characteristics, which is the focus of this work, to foster better API documentation, development practices, testing, debugging, repairing, and verification frameworks. To conduct this study, we take the following major steps. First, we construct a set of 186 real-world Akka actor bugs from Stack Overflow and GitHub via manual analysis of 3,924 Stack Overflow questions, answers, and comments and 3,315 GitHub commits, messages, original and modified code snippets, issues, and pull requests. Second, we manually study these actor bugs and their fixes to understand and classify their symptoms, root causes, and API usages. Third, we study the differences between the commonalities and distributions of symptoms, root causes, and API usages of our Stack Overflow and GitHub actor bugs. Fourth, we discuss real-world examples of our actor bugs with these symptoms and root causes. Finally, we investigate the relation of our findings with those of previous work and discuss their implications. A few findings of our study are: (1) symptoms of our actor bugs can be classified into five categories, with Error as the most common symptom and Incorrect Exceptions as the least common, (2) root causes of our actor bugs can be classified into ten categories, with Logic as the most common root cause and Untyped Communication as the least common, (3) a small number of Akka API packages are responsible for most of API usages by our actor bugs, and (4) our Stack Overflow and GitHub actor bugs can differ significantly in commonalities and distributions of their symptoms, root causes, and API usages. While some of our findings agree with those of previous work, others sharply contrast.This publication has 54 references indexed in Scilit:
- Parallel actor monitors: Disentangling task-level parallelism from data partitioning in the actor modelScience of Computer Programming, 2014
- Why Do Scala Developers Mix the Actor Model with other Concurrency Models?Lecture Notes in Computer Science, 2013
- What are developers talking about? An analysis of topics and trends in Stack OverflowEmpirical Software Engineering, 2012
- Automated, highly-accurate, bug assignment using machine learning and tossing graphsJournal of Systems and Software, 2012
- TransDPOR: A Novel Dynamic Partial-Order Reduction Technique for Testing Actor ProgramsLecture Notes in Computer Science, 2012
- Inferring ownership transfer for efficient message passingACM SIGPLAN Notices, 2011
- Evaluating Ordering Heuristics for Dynamic Partial-Order Reduction TechniquesLecture Notes in Computer Science, 2010
- The Problem with ThreadsComputer, 2006
- Automated Systematic Testing of Open Distributed ProgramsLecture Notes in Computer Science, 2006
- Concurrent programming using actors: Exploiting large-scale parallelismLecture Notes in Computer Science, 1985