diff options
| author | Dianne Hackborn <hackbod@google.com> | 2015-06-22 17:52:13 -0700 |
|---|---|---|
| committer | Dianne Hackborn <hackbod@google.com> | 2015-06-22 17:52:13 -0700 |
| commit | fde298e738310cce29bac5e271bc6b59076f019f (patch) | |
| tree | 58d27988e298af85baa15349ac8b5cc3f61d67b1 /core/java/android | |
| parent | 9622c0cc900da84c903f0395053dd4d9a9e4f53d (diff) | |
Fix issue #21254610: StrictMode uses Log.wtf which crashes apps on L+
Raise the limit at which we consider the strict mode trace to
be unreasonably large.
Change-Id: I5ec5332dd5aa2631e017d246e4a8b978b82cf318
Diffstat (limited to 'core/java/android')
| -rw-r--r-- | core/java/android/os/StrictMode.java | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/core/java/android/os/StrictMode.java b/core/java/android/os/StrictMode.java index 1cc2d334c477..f10b982af750 100644 --- a/core/java/android/os/StrictMode.java +++ b/core/java/android/os/StrictMode.java @@ -1919,9 +1919,9 @@ public final class StrictMode { for (int i = 0; i < numViolations; ++i) { if (LOG_V) Log.d(TAG, "strict mode violation stacks read from binder call. i=" + i); ViolationInfo info = new ViolationInfo(p, !currentlyGathering); - if (info.crashInfo.stackTrace != null && info.crashInfo.stackTrace.length() > 10000) { + if (info.crashInfo.stackTrace != null && info.crashInfo.stackTrace.length() > 30000) { String front = info.crashInfo.stackTrace.substring(256); - // 10000 characters is way too large for this to be any sane kind of + // 30000 characters is way too large for this to be any sane kind of // strict mode collection of stacks. We've had a problem where we leave // strict mode violations associated with the thread, and it keeps tacking // more and more stacks on to the violations. Looks like we're in this casse, |