Memory Leak

... is found! At least the one related to the constant updating of the current skill in training.

I literally spent my whole afternoon tracking it with the help of Instruments. Very frustrating, to say the least. The culprit? The NSUndoManager with its unlimited levels of undoing. I was pretty much asking for the memory to be eaten. Even Objective-C's own garbage collector wouldn't have caught this.

For now I just set the context's undo manager to nil. Nothing I'm doing requires any kind of undoing. If later on this needs to be changed, it's a relatively simple fix.

Tomorrow I'll try to focus on finding any memory leaks related to updating the core data store. Hopefully this one is easier to track. And with the undo manager out of the way, I won't run into the same problem. On the plus side, I'm hoping, not having an undo manager will speed up performance by a noticeable amount.

On a side note, I'm finding that at this stage of development I'm spending far more time debugging and optimizing then I am adding new features. I hope that after a beta release this will change for a bit as I find adding new stuff is far more fun to do.