This is a companion discussion topic for the original entry at https://www.raywenderlich.com/1876614-coordinator-design-pattern-memory-management
This is a companion discussion topic for the original entry at https://www.raywenderlich.com/1876614-coordinator-design-pattern-memory-management
The KanjiDetailViewController stays in memory when going back (deinit is not called). It will only be deallocated once the kanjiDetailViewController property in KanjiDetailCoordinator is set again.
Is this the expected behavior?
@hococoder Can you please help with this when you get a chance? Thank you - much appreciated! :]
It would be great if the Wenderlich team would take the time to answer questions related to the videos. Thanks.
My apologies! This has been on my list of things to respond to but work and life keep getting in the way. It’s early morning here, so let me pull up the code again and look at it here in a little bit, and I’ll respond a bit later.
@hococoder could you reproduce the issue that I mentioned?
@hococoder Do you have any feedback about this? Thank you - much appreciated! :]
This video - https://www.raywenderlich.com/1876614-coordinator-design-pattern-memory-management is just too blurry, even on 1080p. Do we have an update to this screencast?
@pepejeria the var KanjiDetailCoordinator in AllKanjiListCoordinator can be changed to ‘weak’ so that the reference is weak, and with that the deinit will be called automatically when detail vc is popped.