chromium/src
0
Fork 0
Code Activity

android_isolated_splits.md: Update that b/172602571 is not fixed.

Browse Source 
Change-Id: Ia26a022859178ed93b63e8bfcdb46e8ee62ca10f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3714278
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Reviewed-by: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1016198}
This commit is contained in:
Andrew Grieve
2022-06-21 15:08:37 +00:00
committed by Chromium LUCI CQ
parent 1f4bb89cec
commit b93843f2ff
1 changed files with 3 additions and 2 deletions

5
docs/android_isolated_splits.md

@ -101,14 +101,15 @@ happens whenever Chrome is updated rather than when the user launches Chrome.
[preemptively run]: https://source.chromium.org/search?q=symbol:DexFixer.needsDexCompile&ss=chromium
[PackageReplacedBroadcastReceiver]: https://source.chromium.org/search?q=symbol:PackageReplacedBroadcastReceiver&ss=chromium
### Conflicting ClassLoaders (Android Pre-S)
### Conflicting ClassLoaders
Missing synchronization can cause the parent ClassLoader of split contexts to
be different from the Application's ClassLoader. This manifests as odd-looking
`ClassCastExceptions` where `"TypeA cannot be cast to TypeA"` (since the two
`TypeAs` are from different ClassLoaders).
Fixed in Android S. Bug: [b/172602571] (Googler only).
Tracked by UMA `Android.IsolatedSplits.ClassLoaderReplaced`. Occurs < 0.05% of
the time.
**Work-around:**