diff options
| author | Ryan Mitchell <rtmitchell@google.com> | 2021-04-27 10:28:28 -0700 |
|---|---|---|
| committer | Ryan Mitchell <rtmitchell@google.com> | 2021-04-28 13:34:13 -0700 |
| commit | 13587931e5e992bfc1082c9114c93f843a67958d (patch) | |
| tree | 39c70563f11502f01461087cec94c9c9eddc6ac5 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | ff68a9adc3454b7cddb2501d8e82bd4b10b2037c (diff) | |
Synchronize native ApkAssets data
If an ApkAssets is created and destroyed before being put into an
AssetManager, the native layer may not have been synchronized in the
thread that does Java object finalization. So when the Java object gets
deleted on the finalization thread, it may see old/unallocated native
data and not delete the native object correctly.
Similar to how we already lock on the native AssetManager whenever
entering the JNI layer, we should also do the same for ApkAssets.
Bug: 186528775
Test: boot and no crashes
Change-Id: I5fcb9e788a9e3cb8baeb92fa6efc882d5bbbf0b0
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions