-
Notifications
You must be signed in to change notification settings - Fork 96
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
getAllClasses() goes in a loop #82
Comments
Hey @andy3a thanks for your report.
I will replace it with a better version and send you a beta this week 👍 |
Just wondering:
I would like to reproduce it in my machine 💻 |
yes, I'm using Alamofire 5.4.3 |
Hey @andy3a if you don't mind, please check out this commit and share with me if it works for you 👍 Changelog
SMP
Cocoapod
|
thanks for you effort @NghiaTranUIT successfully deployed the commit. I'll need to use it for couple days to see if the issue can be reproduced unless you know how to reproduce the situation when the issue appeared in previous version cheers |
hi @NghiaTranUIT, |
It's odd that this array of AnyClass doesn't release when it exits the function 🤔 @andy3a Please try this commit |
Hi @NghiaTranUIT, I'm sorry but the issue has been reproduced again. ... for the latest fix provided I could provide some details form Profiler if needed. Feel free to request the data you may need for investigation. p.s. could it be like I do smth wrong? itbh I don't see where I could do anything wrong, but maybe you have an idea... Andy |
Hi Nghia,
I faced with the situation when device/simulator starts consuming huge memory amount and hangs as a result. I don't know why this happens, because this is not a persistent issue and it appears from time to time (I don't see specific cause).
This is the evidence from Debug navigator:
And as per profiler looks like getAllClasses is responsible for that:
so there are more than 40 000 calls of it...
device iOS version: 14.6 (reproduced for simulators as well)
Xcode: Version 12.5.1 (12E507)
please let me know I should provide some more details
Thanks,
Andrew
The text was updated successfully, but these errors were encountered: