# A Benchmark of Data Loss Bugs for Android Apps

**Authors:** Oliviero Riganelli, Marco Mobilio, Daniela Micucci, Leonardo Mariani

arXiv: 1905.11040 · 2019-05-28

## TL;DR

This paper introduces a comprehensive benchmark of 110 data loss bugs in Android apps, providing a valuable resource for researchers to analyze and develop solutions for state management issues.

## Contribution

It systematically collects and shares a benchmark dataset of Android data loss bugs, including faulty and fixed apps, test cases, and supporting information.

## Key findings

- Benchmark includes 110 data loss faults in Android apps.
- Provides automated test cases for reproducing bugs.
- Available on GitLab for research use.

## Abstract

Android apps must be able to deal with both stop events, which require immediately stopping the execution of the app without losing state information, and start events, which require resuming the execution of the app at the same point it was stopped. Support to these kinds of events must be explicitly implemented by developers who unfortunately often fail to implement the proper logic for saving and restoring the state of an app. As a consequence apps can lose data when moved to background and then back to foreground (e.g., to answer a call) or when the screen is simply rotated. These faults can be the cause of annoying usability issues and unexpected crashes. This paper presents a public benchmark of 110 data loss faults in Android apps that we systematically collected to facilitate research and experimentation with these problems. The benchmark is available on GitLab and includes the faulty apps, the fixed apps (when available), the test cases to automatically reproduce the problems, and additional information that may help researchers in their tasks.

## Full text

_Full body text omitted from this summary view._ Fetch the complete paper as Markdown: https://tomesphere.com/paper/1905.11040/full.md

## Figures

4 figures with captions in the complete paper: https://tomesphere.com/paper/1905.11040/full.md

## References

14 references — full list in the complete paper: https://tomesphere.com/paper/1905.11040/full.md

---
Source: https://tomesphere.com/paper/1905.11040