@Aleksey Gureiev: A simple application with the table view in the main window shows it all. During the window resizing event handling, the internals of Cocoa allocate so many strings and integers that I run out of memory in less than 30 seconds
It's hard to say what's going on without looking at actual code, but it would be unusual to run out of memory so easily in the circumstances you describe. Xcode, for example, is an incredibly complex app with some unusual memory needs which runs under GC.
It's possible that some minor tweaks to your code could work wonders. It's not uncommon for new Mac programmers to run into discouraging but easily-fixed errors early on in their work. I've spoken to countless individuals who told me that Core Data or Cocoa was lacking in some way, only to discover that they had made some wildly incorrect assumptions about how the language and frameworks behave.
I'm not saying this is necessarily the case for you, but you'd be in the company of some very talented programmers if it was.
by Scott Stevenson — Nov 08
It's hard to say what's going on without looking at actual code, but it would be unusual to run out of memory so easily in the circumstances you describe. Xcode, for example, is an incredibly complex app with some unusual memory needs which runs under GC.
It's possible that some minor tweaks to your code could work wonders. It's not uncommon for new Mac programmers to run into discouraging but easily-fixed errors early on in their work. I've spoken to countless individuals who told me that Core Data or Cocoa was lacking in some way, only to discover that they had made some wildly incorrect assumptions about how the language and frameworks behave.
I'm not saying this is necessarily the case for you, but you'd be in the company of some very talented programmers if it was.