[native] Fix loading of shared libraries directly from the APK #10437
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #10383
This is an optimization for when shared libraries aren't extracted from the APK.
In this case, we can load them faster by using extended dlopen API provided by
Android, which allows us to skip path scanning by
dlopen
.This is done by recording file offset of any .so library inside the APK at
application startup and then using it, together with the APK file descriptor
that we keep around, to load the library using Android extended version of
dlopen
.This does not apply to any libraries using JNI, as they have to be loaded
using the Java
System.loadLibrary
API (see cba39dc and 1a62af3)