Have things changed now?: an empirical study of bug characteristics in modern open source software

By Zhenmin Li, Lin Tan, Xuanhui Wang, Shan Lu, Yuanyuan Zhou, Chengxiang Zhai. International Conference on Anti-counterfeiting, Security, and Identification, 2006

321 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Understanding and detecting real-world performance bugs (2012, methodology): “(3) The percentage of synchronization problems among performance bugs in our study is higher than the percentage of synchronization problems among functional bugs in a previous study for a similar set of applications [29] (Section 4.”
A large scale study of programming languages and code quality in github (2014, background): “Previous researches term these errors as Software Component bug [20, 33].”
An empirical analysis of flaky tests (2014, background): “Most empirical studies of bugs start from bug reports [8,14,22,24,28].”
Predicting vulnerable software components (2007, background): “[17] have studied how the numbers of defects and security issues evolve over time.”
Predicting defects using network analysis on dependency graphs (2008, unknown): “D.2.9 [Software Engineering]:”
Learning from mistakes: a comprehensive study on real world concurrency bug characteristics (2008, unknown): “In contrast, in many bug reports about memory bugs, programmers mentioned that they got help from Valgrind, Purify, etc [20].”