-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.UnsatisfiedLinkError: com.facebook.imagepipeline.memory.NativeMemoryChunk #2131
Comments
A user's mobile phone model is vivo X6S A. When the app is opened, the app will flash back and the UnsatisfiedLinkError will be reported,The error disappeared when I changed the version of fresco from 1.9.0 to 1.5.0 |
have encountered the same problem fresco:1.9.0 java.lang.UnsatisfiedLinkError: com.facebook.imagepipeline.memory.NativeMemoryChunk |
+1 |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "bug" or "enhancement" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to reopen with up-to-date information. |
It's still issue with the latest release.
Device model : 100% is Oppo version 5.
Please help |
We use GitHub Issues for bugs.
If you have a non-bug question, please ask on Stack Overflow: http://stackoverflow.com/questions/tagged/fresco
--- Please use this template, and delete everything above this line before submitting your issue ---
Description
java.lang.UnsatisfiedLinkError:There are many people who have this problem and don't know what caused it. Please help me solve this problem. I can't build multiple APKs,Because we have introduced the SDK of ali baichuan e-commerce company in our application, only one security picture is assigned to an app when signing,
I can't change abiFilters in app/build.gradle , If I change it,the security picture will be invalid,and This security picture cannot be replaced;I have tried #2049 (especially #2049 (comment)). and can't solve my problem
implementation 'com.facebook.fresco:fresco:1.9.0'
implementation 'com.facebook.fresco:imagepipeline-okhttp3:1.9.0'
Reproduction
error log:

java.lang.UnsatisfiedLinkError: com.facebook.imagepipeline.memory.NativeMemoryChunk
at com.facebook.imagepipeline.memory.NativeMemoryChunkPool.alloc(NativeMemoryChunkPool.java:56)
at com.facebook.imagepipeline.memory.NativeMemoryChunkPool.alloc(NativeMemoryChunkPool.java:18)
at com.facebook.imagepipeline.memory.BasePool.get(BasePool.java:255)
at com.facebook.imagepipeline.memory.NativePooledByteBufferOutputStream.(NativePooledByteBufferOutputStream.java:49)
at com.facebook.imagepipeline.memory.NativePooledByteBufferFactory.newByteBuffer(NativePooledByteBufferFactory.java:96)
at com.facebook.imagepipeline.memory.NativePooledByteBufferFactory.newByteBuffer(NativePooledByteBufferFactory.java:24)
at com.facebook.imagepipeline.cache.BufferedDiskCache.readFromDiskCache(BufferedDiskCache.java:334)
at com.facebook.imagepipeline.cache.BufferedDiskCache.access$400(BufferedDiskCache.java:34)
at com.facebook.imagepipeline.cache.BufferedDiskCache$2.call(BufferedDiskCache.java:180)
at com.facebook.imagepipeline.cache.BufferedDiskCache$2.call(BufferedDiskCache.java:164)
at bolts.Task$4.run(Task.java:357)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at com.facebook.imagepipeline.core.PriorityThreadFactory$1.run(PriorityThreadFactory.java:51)
at java.lang.Thread.run(Thread.java:818)[FILL THIS OUT: How can we reproduce the bug? Provide URLs to relevant images if possible, or a sample project.]
Solution
[OPTIONAL: Do you know what needs to be done to address this issue? Ideally, provide a pull request which fixes this issue.]
Additional Information
The text was updated successfully, but these errors were encountered: