Skip to content
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

Crash due to memory issue iOS & Android #421

Open
marf opened this issue Feb 26, 2019 · 6 comments
Open

Crash due to memory issue iOS & Android #421

marf opened this issue Feb 26, 2019 · 6 comments

Comments

@marf
Copy link

marf commented Feb 26, 2019

Hello,
I am heavily using Fast Image in my app since I have large lists (with 300+ elements) to render with an image on the every item.

I have noticed that on old devices for example iPhone 6, 5s etc. and a lot of Android phones the app crashes and in Xcode (for iPhones) the crash reported: Memory issue

If I remove fast image and use normal Image component the crash dissapear.

What should I do?
Is this due to a memory leak?

I have tried to follow this #371 which reports how to fix memory leaks but it does not work.

What should I do?

Best regards,
Marco

@StevenMasini
Copy link

Hi @marf

My previous PR was only for iOS, I don't know if there is memory leaks on Android, and if there is I don't know what cause them neither.

Can I ask you to try to see if my new PR #433 at least fix the memory leak on iOS for you ?

I remember you said you couldn't compile #371 before, and I found out that there is a bug with npm & yarn. I put instruction about how to try my PR in the comment.

Please try it out and let me know.

@evanjmg
Copy link

evanjmg commented Apr 7, 2019

I think I'm still getting crashes due to memory? The crashes are very few and these devices have less than 5% memory left on device.

Fatal Exception: NSInvalidArgumentException-[UIViewAnimationState url]: unrecognized selector sent to instance 0x110c428e0 Raw Text
--
0 | CoreFoundation | __exceptionPreprocess
4 | CoreFoundation | _CF_forwarding_prep_0
5 | FFFastImageView.m line 79-[FFFastImageView imageDidLoadObserver:]

@StevenMasini
Copy link

@evanjmg

Fatal Exception: NSInvalidArgumentException-[UIViewAnimationState url]: unrecognized selector sent to instance 0x110c428e0 Raw Text

This isn't related to memory leak error. Most likely what you said here #433 (comment)

@ammoradi
Copy link

any news about this?
in Android, using this lib causing huge memory usage and crashes on low-android-versions devices!

@afeichuanqi
Copy link

关于这个的任何消息?
安卓中,使用此lib中会导致大量内存使用并在低版本的Android的设备上崩溃!

is there any news

@Mihai-github
Copy link

Hi guys,

I've recently started using this library and for IOS I don't have any issues yet... but on Android, even with new phones like Samsung S20 or S21 I have problems with memory leaks and I don't know if someone figured out how to solve this problem or if the library said it's gonna make something about this problem.

I also have to mention that the page where the problem happens is a big component that has many requests in and out and for sure this may also add to this problem I think, but still, I hope someone can help me with this problem because is fast image load and the cache is nice to have where you display a lot of images and need speed.

Thanks!.

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

No branches or pull requests

6 participants