-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Strong And Weak Reference Issue (MemoryLeak) #83
Comments
@farshadmb I'll have a look and see if I can pinpoint which component the memory leak is occurring in. Agree it's a pretty critical issue! |
@msaps I can provide the sample project and I will send to your mail |
@farshadmb okay cheers! Probably easier to upload as an attachment on this please. Emails are easier to lose! 😄 |
@farshadmb thanks!! 👍 Merged, and I'll get it in |
@msaps your welcome dude |
Fixed as of 1.3.2. |
@farshadmb really appreciate all the work! 👍 |
@msaps now we can go to |
@msaps Hi man
Here I am again 😊 😁
I found another issue that is critical in my opinion. The "Tabman" or "Pageboy", I do not know exactly. However, you use some strong reference cause appear this issue.
For Simulate what happened to me. Please Use
NavigationController
as applicationrootViewController
then push object which inherits from "Tabman" library.After that back to
rootViewController
ofNavigationController
. The "Tabman" or "Pageboy" must be deallocated after popTabmanViewController
orPageboyViewController
but never called deinitNote: declare
deinit
function in "Tabman" or "Pageboy" or A class inherit from bothdeinit{ print("\(self)")
print self for debug log of the memory address.
The text was updated successfully, but these errors were encountered: