diff options
| author | wilsonshih <wilsonshih@google.com> | 2018-08-20 10:36:25 +0800 |
|---|---|---|
| committer | wilsonshih <wilsonshih@google.com> | 2018-08-22 09:43:55 +0800 |
| commit | 0042e4516ffcea66cb209d8c2dad7aeaa53b50fb (patch) | |
| tree | eca184b0eabb5bbf9fa76a233032a3fd6ba186aa /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | a2e28a4b86409415e84d36fcc072e6c3c2f0e561 (diff) | |
Prevent ViewRootImpl.mDisplay become null.
For some timing cases client side may not get desired display with old
displayId.
For this issue, client side has just received configuration change and
handle it in ActivityThread#handleActivityConfigurationChanged. At the
same time, DisplayManagerService was about to destory display. When
ViewRootImpl want to update display with new DisplayAdjustments, it got
null because the old displayId was removed.
For this scenario, fallback to use default display. Usually there should
be other displayId change event comes from server side to ask client update.
Change-Id: Ifb843f82b753761cb6306e7482b38a0ffd89498d
Fix: 73558361
Test: atest CtsWindowManagerDeviceTestCases
Test: atest CtsActivityManagerDeviceTestCases
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions