NSTableView with tableViewSelectionDidChange Delegate ... Memory Leak?
NSTableView with tableViewSelectionDidChange Delegate ... Memory Leak?
- Subject: NSTableView with tableViewSelectionDidChange Delegate ... Memory Leak?
- From: Richard Kendall Wolf <email@hidden>
- Date: Fri, 7 Jun 2002 16:26:06 -0500
I have been wrestling with this problem for the past twenty-four hours,
but I am not sure it even -is- a problem. I have checked Apple's
documentation and this mailing list's archives at
http://cocoa.mamasam.com (whoever runs this site, you are doing a
wonderful thing!), but haven't seen any mention of the phenomenon I'm
about to describe. I am still in the process of learning Cocoa, so
hopefully you wiser heads out there will have some insight.
I've been working with a small program that has an NSTableView. My code
implements a delegate method, tableViewSelectionDidChange, and it works
just fine. However, because I am new to Cocoa, I want to make sure that
I'm doing this right. So, I run MallocDebug and top to see if I'm
leaking memory. And, if I click and drag over table rows, continuously
(just for the heck of it), the amount of private memory (RPRVT in top)
goes up, but never goes down, even when I stop dragging over multiple
rows (it maintains whatever value it had when I stop dragging over
rows). I thought it might be doing something funky in my code, so I
went back to a simpler example ... RaiseMan in Chapter 5 of Aaron
Hillegass' book. I noticed exactly the same behavior. However,
Mail.app which, ostensibly, uses an NSTableView with delegates does not
display the same behavior. Using Aaron's code as reference, what are we
doing that Mail.app is not (or vice versa)? Is this even something I
should be particularly worried about?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.