summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/FieldPacker.java
diff options
context:
space:
mode:
authorlouis_chang <louis_chang@htc.com>2015-03-31 15:18:21 +0800
committerlouis_chang <louis_chang@htc.com>2015-03-31 15:18:21 +0800
commit5064fddf81e477a90c81d72f7328aa5887c67511 (patch)
tree43d04bfa922e87756da75cf1e911588b2e8c7a9f /rs/java/android/renderscript/FieldPacker.java
parentee80414d0ddd6a27bbf86e0de47dd86bc335431d (diff)
[ActivityManager] Examine bad process before clean up application
record Symptom: Unable to launch activity Root cause: There are some cases that would start process while pid assigned or already running. So the previous application record will be clean up via handleAppDiedLocked(), but it won't be removed from ActivityManager.mProcessNames since the process is supposed to be restart later. However, if the process is started from a background operation and has named as a bad process, it silently fail the launch. Then, the process won't ever be request to start afterward. The process status is app.pid > 0 and app.thread is null. The application components are unable to launch since then. Solution: Examine bad process before clean up application record Change-Id: I53dc06e49254094abc06e460c8b8b33f36803601
Diffstat (limited to 'rs/java/android/renderscript/FieldPacker.java')
0 files changed, 0 insertions, 0 deletions