4

I have a question on the ownership of windows vs view controllers and when they're released. I created a test project, and only added one line of code to the NSViewController: 

deinit { print("ViewController Dismissed.") }

Why isn't this called when I close the window? I profiled it in Instruments and there aren't any memory leaks, but there is a reference to the ViewController still.

Also, I tried the "Release when closed" option on the NSWindow, still no dice. Can anyone help with understanding this? Thanks!!

Screenshot from Instruments

JoeBayLD
  • 939
  • 2
  • 10
  • 25

2 Answers2

0

I would have simply put this as a comment, but I don't have enough reputation:

Could there be a closure in your view controller that is maintaining a strong reference to your view controller or some object in your controller? That is one way a retain cycle can be created. If that was it, I would think it would show up in instruments, but it's just a thought.

Also, is your view controller part of any kind of larger navigation system, such as a tab bar controller? That could be a factor. I'm not sure.

user2807654
  • 122
  • 1
  • 1
  • 11
0

As I know your running app always have the strong reference to a window instance, which in turn has the reference to a view controller. If you go to the Debug View Hierarchy after closing your window, you'll still see it there.If you remove storyboard entry point to that window in your storyboard, you wont have that window at all.

Eugene Gordin
  • 4,047
  • 3
  • 47
  • 80
  • Right. Well I guess I'm looking to release the view controller somehow, because it's retaining a lot of references and memory for other objects (in my actual project, not the test one). Any ideas how? – JoeBayLD Mar 08 '16 at 08:41
  • To add to that. I did look at the Debug View Hierarchy, and the window is still there and doing work. Trying to get rid of it.. Thanks – JoeBayLD Mar 08 '16 at 09:18