diff options
| author | 2021-10-13 15:37:55 +0100 | |
|---|---|---|
| committer | 2021-10-15 08:18:25 +0000 | |
| commit | 251dc7d5c33469f8510318fb564f0b9ee875e2d4 (patch) | |
| tree | f5ab26fe57ff45620747383d3c3eaff179a4bbf6 /libnativebridge/tests/NativeBridge3LoadLibraryExt_test.cpp | |
| parent | c99811a1b31512635f51ef0007b8329b77a4c759 (diff) | |
Do not run background verification on unknown class loaders.
There can be races between the Java threads and the background
verification thread when verifying classes. The Java threads are allowed
to load classes while verifying, but the background verification thread
cannot. Which means we can be in situations where the background
verification sees, for example, a concrete j.l.Integer but an unresolved
j.l.Number.
Test: 833-background-verification
Bug: 202463489
Merged-In: I5aadb9d5ee79003b3d8200571cecd0819e13bd64
(cherry picked from commit ba2ff159676df24e0265804fbad6f092997f93bc)
Change-Id: I75b7d1a2d4e952fc66033f49c097246cb55511a5
Diffstat (limited to 'libnativebridge/tests/NativeBridge3LoadLibraryExt_test.cpp')
0 files changed, 0 insertions, 0 deletions