-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Failure to render image: RecyclableBufferedInputStream$InvalidMarkException #4517
Comments
This confirms my tests on reported issues that was not fully able to reproduce: Seems side effect of 2b61482#diff-bef6c4ca8f43cb29b8856a5a0adf3e70729ce4e8eb885f2de42031e58dce7683 that is a 4.12 change. And fix worse than issue. Ping @sjudd |
I do not believe this bug is specific to 4.12. Signal is using 4.11 in production, which also has this issue. I just used 4.12 in the sample project to verify that the bug wasn't fixed in that version :) |
Arf thanks for info :( I have users that report missing images since I updated but none of them do contact me with logs :( I guess I'll keep praying one of those report do read Play Store answer :( |
@greyson-signal thanks for the detailed report. @Tolriq if you do get more specific reports and especially any sample images where the issue reproduces, please let me know. Assuming I'm understanding this correct, this is not caused by 2b61482#diff-bef6c4ca8f43cb29b8856a5a0adf3e70729ce4e8eb885f2de42031e58dce7683, but that fix was related to the same category of memory/buffer issues. Here's the confluence of issues that causes bugs like this one:
I believe the specific issue in this bug could be fixed by While investigating this, I also realized that while we support simple FileDescriptors, we do not support AssetFileDescriptors because AssetFileDescriptors have TL;DR:
|
Any update about it? |
I'm getting the same issue with 4.13.0:
Reverting to 4.11.0 fixed the issue. |
Hi there! Over at Signal a user reported an issue around being unable to render a specific image. Sure enough the problem seems to be completely reproducible with that image.
I made a POC app to verify it wasn't anything Signal was doing:
https://github.com/greyson-signal/glide-failure-poc
The POC shows Glide loading a working image and also failing to load the image from the issue.
Thanks!
Glide Version:
4.12.0
Integration libraries:
None
Device/Android Version:
Android 10 emulator, my Android 11 Pixel 5. In general seems to be a universal issue.
Issue details / Repro steps / Use case background:
Image fails to load, but renders in a web browser and can otherwise be opened in desktop image programs.
Glide load line /
GlideModule
(if any) / list Adapter code (if any):See POC
Layout XML:
See POC
Stack trace / LogCat:
The text was updated successfully, but these errors were encountered: