-
Notifications
You must be signed in to change notification settings - Fork 525
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
Bug with AlamoFireImage #75
Comments
Is it possible for your to provide some of your calling code? We're unlikely to be able to fix this without knowing how it's triggered. |
Here is my calling code:
On this call i only download 4 images. Need any other info? let me know |
Is there any chance you could submit a sample project that reproduces this behavior @patchthecode? That would make it much easier to diagnose if there's actual an AFI issue here or something with your logic. Nothing you posted in your example looks problematic. |
ok, its part of a larger project. I will scale out the problem part and submit it in a while |
After thinking through this some more, I'm almost positive this is due to the non-thread safe UIImage initializer. I'm going to switch the response serializer over to using the thread-safe initializer. I should have done this right from the start. |
Should be resolved with 85048ff. @patchthecode, if you could retest with the latest commits on |
I'll gladly re-open this issue if the problem persists. |
Ok. I am using this framework from cocoa pods. I just did a 'Pod Install' to update the framework. |
Are you loading any other images using |
No i am not loading any other images outside of alamoFireImage. However, i just looked at what you said about the release number. Seems i was still using version 2.2 in my Cocoapod file. I have now changed version to *** pod 'AlamofireImage', '~> 2.3' *** and did an update. It the error happens again after this update, then i will just give you a copy of the problem code so that you can run it. Thanks for the help. Will update you if it happens again after the update. |
Update: Since after updating. No more crashes. And i'm not get the BOMStorage file warning messages anymore. All seems well. Thanks for your work. Have a good one. |
That's great to hear @patchthecode! Thanks for reporting that back to us. |
myProg(63494,0xb029b000) malloc: *** error for object 0x79b5ce80: double free
*** set a breakpoint in malloc_error_break to debug
The text was updated successfully, but these errors were encountered: