History log of /frameworks/base/services/java/com/android/server/am/NativeCrashListener.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
1b2d59500a8c066dec413f906c480ee46f004df5 19-Jun-2013 Nick Kralevich <nnk@google.com> NativeCrashListener: fix file descriptor leak.

Sending thousands of crashes can result in the system
eventually running out of file descriptors. Close file
descriptors after we're done with them.

Change-Id: I09ae9ce36426ded3fd591dda9a3550a19c2f01d3
/frameworks/base/services/java/com/android/server/am/NativeCrashListener.java
be4e6aaa0252dd7da28b7aa85beba982538efa46 07-Jun-2013 Dianne Hackborn <hackbod@google.com> Initial super-primitive process tracker.

The goal of this is to keep track of what app processes
are doing, to determine who is being abusive, when the system
is getting into memory constrained situations, and help the
user determine how to resolve this.

Right now it doesn't really do any of that, just keeps track
of how long every process has been running since boot.

Also update the activity manager to use "cached" as the terminology
for what it used to interchangeably call hidden and background
processes, and switch ProcessMap over to using ArrayMap.

Change-Id: I270b0006aab1f38e17b7d9b65728679173c343f2
/frameworks/base/services/java/com/android/server/am/NativeCrashListener.java
b86d81d3ff1beb46b18795edbbb8850e9cde4c98 20-Apr-2013 Christopher Tate <ctate@google.com> Don't attempt native crash reporting for persistent apps

Bug 8639127

Change-Id: I55035cfed9ba04597422f675ede105dae40b2fbf
/frameworks/base/services/java/com/android/server/am/NativeCrashListener.java
1b645986020a5bd66f6783fa87b9f084c809d801 17-Apr-2013 Christopher Tate <ctate@google.com> Lengthen the AM timeout reading crash reports slightly

We're missing some (small fraction of) native crash reports from
debuggerd. It looks like under high system load the debuggerd
reporting code just isn't quite timely enough for the very short
timeouts initially deployed, so lengthen those a bit.

Bug 8552010

Change-Id: Icbc5b6517de3bb98fff1af2ea42ffd208ef20412
/frameworks/base/services/java/com/android/server/am/NativeCrashListener.java
88d842cf8a3adcae5cd2d243dcc182c96f40db29 09-Apr-2013 Eric Rowe <erowe@google.com> Change dropbox tag for native crashes.

Change-Id: Id2738fc758c3d144e5fdd2c7f1c8617dad129338
/frameworks/base/services/java/com/android/server/am/NativeCrashListener.java
58d380d2af8079075e4773a3e5ca6c2820760e3d 19-Mar-2013 Christopher Tate <ctate@google.com> debuggerd now notifies the Activity Manager about native crashes

The Activity Manager sets up a permission-guarded domain socket, which
debuggerd connects to when a crash happens. If this is successful,
the daemon then mirrors the logged crash report to that socket, then
closes it.

The Activity Manager parses the native crash dump supplied by debuggerd
and forwards it to the standard app-crashed code. The UX result is
that users now see the normal "app has stopped unexpectedly" dialog
with "report" and "okay" options for native crashes, not just for
DVM-mediated crashes.

Bug 8322568

Change-Id: Ie1b279896c603bd74d82d6cfcfd66a8f231da134
/frameworks/base/services/java/com/android/server/am/NativeCrashListener.java