Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Don't wtf when rects are not available

Browse Source 
No reason to freak out about this - this isn't that dramatic such
that it should affect our system stability metrics.

Test: Boot device
Bug: 35633644
Change-Id: I70f4303b315376f6c80edd199473b9218f718a8c
This commit is contained in:
Jorim Jaggi
2017-03-14 20:15:59 +01:00
parent 4fd2455141
commit 2550f3f787
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
services/core/java/com/android/server/wm/AppTransition.java
View File

@@ -692,7 +692,7 @@ public class AppTransition implements Dump {
private void getDefaultNextAppTransitionStartRect(Rect rect) {
if (mDefaultNextAppTransitionAnimationSpec == null ||
mDefaultNextAppTransitionAnimationSpec.rect == null) {
Slog.wtf(TAG, "Starting rect for app requested, but none available", new Throwable());
Slog.e(TAG, "Starting rect for app requested, but none available", new Throwable());
rect.setEmpty();
} else {
rect.set(mDefaultNextAppTransitionAnimationSpec.rect);
@@ -705,7 +705,7 @@ public class AppTransition implements Dump {
spec = mDefaultNextAppTransitionAnimationSpec;
}
if (spec == null || spec.rect == null) {
Slog.wtf(TAG, "Starting rect for task: " + taskId + " requested, but not available",
Slog.e(TAG, "Starting rect for task: " + taskId + " requested, but not available",
new Throwable());
rect.setEmpty();
} else {