diff options
| author | Jeff Sharkey <jsharkey@android.com> | 2016-05-02 12:33:22 -0600 |
|---|---|---|
| committer | Jeff Sharkey <jsharkey@android.com> | 2016-05-02 12:33:24 -0600 |
| commit | 9540ca4fc47ac5448826c43912aa573caecc746c (patch) | |
| tree | 7bfa164be09ea7eba34d0d69cd2e3d96b0b7fbfd /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | b9f7541d9bd8b0b37f04ea8244a8d0bd5fb97717 (diff) | |
When fork() fails, clean up data structures.
There are a number of different conditions that could cause
ActivityManager to fail to fork() a process. One of the most common
ones is a package being "frozen" during a PackageManager operation.
When this happens, use the common forceStopPackageLocked() method
to cleanup any internal bookkeeping structures. (It's slightly
misnamed, since it doesn't actually "force stop" the app.) It's
also the same method that we called moments earlier when the package
was first frozen through KILL_APPLICATION_MSG.
Bug: 28395549
Change-Id: I7b1623c5f66fc1de24cad5360c977ea764d09244
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions