SPLASH 2020
Sun 15 - Sat 21 November 2020 Online Conference
Tue 17 Nov 2020 11:40 - 12:00 at OOPSLA/ECOOP - T-3
Tue 17 Nov 2020 23:40 - 00:00 at OOPSLA/ECOOP - T-3

Mobile operating systems, especially Android, expose apps to a volatile runtime environment. The app state that reflects past user interaction and system environment updates (e.g., battery status changes) can be destroyed implicitly, in response to runtime configuration changes (e.g., screen rotations) or memory pressure. Developers are therefore responsible for identifying app state affected by volatility and preserving it across app lifecycles. When handled inappropriately, the app may lose state or end up in an inconsistent state after a runtime configuration change or when users return to the app.

To free developers from this tedious and error-prone task, we propose a systematic solution, LiveDroid, which precisely identifies the necessary part of the app state that needs to be preserved across app lifecycles, and automatically saves and restores it. LiveDroid consists of: (i) a static analyzer that reasons about app source code and resource files to pinpoint the program variables and GUI properties that represent the necessary app state, and (ii) a runtime system that manages the state saving and recovering. We implemented LiveDroid as a plugin in Android Studio and a patching tool for APKs. Our evaluation shows that LiveDroid can be successfully applied to 966 Android apps. A focused study with 36 Android apps shows that LiveDroid identifies app state much more precisely than an existing solution that includes all mutable program variables but ignores GUI properties. As a result, on average, LiveDroid is able to reduce the costs of state saving and restoring by 16.6X (1.7X - 141.1X) and 9.5X (1.1X - 43.8X), respectively. Furthermore, compared with the manual state handling performed by developers, our analysis reveals a set of 46 issues due to incomplete state saving/restoring, all of which can be successfully eliminated by LiveDroid.

Tue 17 Nov
Times are displayed in time zone: Central Time (US & Canada) change

11:00 - 12:20: T-3OOPSLA at OOPSLA/ECOOP +12h
11:00 - 11:20
Talk
OOPSLA
Ritwika GhoshUIUC, Chiao HsiehUniversity of Illinois at Urbana-Champaign, Sasa MisailovicUniversity of Illinois at Urbana-Champaign, sayan mitraUniversity of Illinois at Urbana-Champaign
Pre-print
11:20 - 11:40
Talk
OOPSLA
Suvam MukherjeeMicrosoft Research India, Pantazis DeligiannisMicrosoft Research, Arpita BiswasIndian Institute of Science, Akash LalMicrosoft Research India
11:40 - 12:00
Talk
OOPSLA
Umar FarooqUniversity of California Riverside, Zhijia ZhaoUC Riverside, Manu SridharanUniversity of California Riverside, Iulian NeamtiuNew Jersey Institute of Technology
Pre-print
12:00 - 12:20
Talk
OOPSLA
Aayan KumarMicrosoft Research India, Vivek SeshadriMicrosoft Research, India, Rahul SharmaMicrosoft Research
23:00 - 00:20: T-3OOPSLA at OOPSLA/ECOOP
23:00 - 23:20
Talk
OOPSLA
Ritwika GhoshUIUC, Chiao HsiehUniversity of Illinois at Urbana-Champaign, Sasa MisailovicUniversity of Illinois at Urbana-Champaign, sayan mitraUniversity of Illinois at Urbana-Champaign
Pre-print
23:20 - 23:40
Talk
OOPSLA
Suvam MukherjeeMicrosoft Research India, Pantazis DeligiannisMicrosoft Research, Arpita BiswasIndian Institute of Science, Akash LalMicrosoft Research India
23:40 - 00:00
Talk
OOPSLA
Umar FarooqUniversity of California Riverside, Zhijia ZhaoUC Riverside, Manu SridharanUniversity of California Riverside, Iulian NeamtiuNew Jersey Institute of Technology
Pre-print
00:00 - 00:20
Talk
OOPSLA
Aayan KumarMicrosoft Research India, Vivek SeshadriMicrosoft Research, India, Rahul SharmaMicrosoft Research