| commit | 44b9c7d92d02448ecdb903b60fcda1458d3a8d6f | [log] [tgz] |
|---|---|---|
| author | Lucas Dupin <dupin@google.com> | Fri Jul 14 11:32:21 2023 -0700 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Jul 19 03:05:51 2023 +0000 |
| tree | 54cf476295bf375c338b1d516956b768a53f3700 | |
| parent | dac52959385b235f3802a5f9749f161118e7e411 [diff] |
Avoid sending messages of destroyed Engine And app can call notifyColorsChanged() on a destroyed engine, which would cause problems, given it doesn't have a surface anymore. The same is true to visibility notification, where the engine can be destroyed before it had the opportuinity of drawing its first frame (if it had to load large assets for example) Test: manually change wallpapers Test: WallpaperServiceTest (both CTS and internal) Fixes: 291053623 (cherry picked from commit 650a7f8afc00885afd6590e07b3a2e4c9ced404e) (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:6f9ac2b1703c62f53cd5c504e1ac7a3371b4fbe9) Merged-In: Iff83603695cff491f2045586d5b3f4658f7ae55a Change-Id: Iff83603695cff491f2045586d5b3f4658f7ae55a