diff options
| author | 2024-01-04 16:15:57 +0000 | |
|---|---|---|
| committer | 2024-01-10 12:48:45 +0000 | |
| commit | ceeff2527f034991d8bb46947643a276bab6e72f (patch) | |
| tree | ce36456262b7cd3d70ba6f3f2673a5835a3a2181 /libs/androidfw/ZipFileRO.cpp | |
| parent | 40cfc64ca76304c207ef69e891c3521f7d5aef25 (diff) | |
Initialize KeyguardViewMediator immediately
KeyguardViewMediator is the main entry point for KeyguardService and
WindowManager, and will receive calls on binder
threads. KeyguardViewMediator has split initialization into 2
parts: in the constructor and in start(). start() may be invoked
multiple seconds after the constructor, which gives the binder calls
an opportunity to make calls on a partially initialized object. I'm
sure this was done for reasons back in the day, but it is now causing
race conditions. To avoid the NullPointerException, move some code into
the constructor for initialization.
Fixes: 308738978
Test: Manual (kill systemui repeatedly and look for errors)
Flag: N/A
Change-Id: Ie2b0771215781852f7648b5bdee7ab09517fd6a6
Diffstat (limited to 'libs/androidfw/ZipFileRO.cpp')
0 files changed, 0 insertions, 0 deletions