Skip to content

Conversation

Unpublished
Copy link
Collaborator

@Unpublished Unpublished commented Apr 1, 2024

Fixes the issue mentioned in #1405 without each view having its own glide instance

Also fixes leaking context via static reference to FavIconHolder


More infos:

Ref: #1405 (comment)
I think the main culprit is having a static FavIconHandler which leaks context.

Using a per fragment instance approach for Glide will still benefit from Glide's lifecycle awareness, pausing requests of not visible fragments. Also fragments context should be aware of configuration changes like theme AFAIK.

Signed-off-by: Unpublished <unpublished@gmx.net>
Signed-off-by: Unpublished <unpublished@gmx.net>
@Unpublished
Copy link
Collaborator Author

@DoHe Can you double check if this branch fixes the issue for you as well?

@DoHe
Copy link

DoHe commented Apr 1, 2024

@Unpublished yes, I can confirm this fixes the favion issues I was seeing 👍

@David-Development
Copy link
Member

@Unpublished Thank you for implementing this so quickly! Looks like a great solution to me. I'm glad that you were able to remove the static reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants