diff options
| author | 2025-03-14 22:05:52 +0000 | |
|---|---|---|
| committer | 2025-03-21 16:38:33 +0000 | |
| commit | d6e56a41da24eb8f6bd0b7a38289c7442421b648 (patch) | |
| tree | a21fe66dcc984ffb78e4c17176a2606b194e714c /libnativebridge/native_bridge.cc | |
| parent | 9126e6fb2137d43bf6363e82b38bbd3edf428f2c (diff) | |
Delete SDM files on "pm delete-dexopt" and "pm compile --reset".
If SDM files are installed and then cleaned up after becoming obsolete,
"pm delete-dexopt" will put the app in a state where there is not dexopt
artifacts to use. Therefore, for consistency in terms of app
performance, we should delete SDM files on "pm delete-dexopt" even if
they are not obsolete.
"pm compile --reset" has a similar situation. If SDM files are installed
and then cleaned up after becoming obsolete, "pm compile --reset" will
put the app in a state where its dexopt artifacts are generated on
device with the cloud profile (ideally, the behavior should be restoring
the SDM files, but that's impossible). Therefore, for consistency in
terms of app performance (assuming locally generated artifacts and cloud
artifacts have different performance), we should delete SDM files and
regenerate dexopt artifacts on device on "pm compile --reset".
Bug: 377474232
Test: atest ArtServiceTests
Change-Id: If1934b6c7da19ad346f4962241bbdab13fa12ce6
Diffstat (limited to 'libnativebridge/native_bridge.cc')
0 files changed, 0 insertions, 0 deletions