Re: Why does this leak memory?
Re: Why does this leak memory?
- Subject: Re: Why does this leak memory?
- From: Charilaos Skiadas <email@hidden>
- Date: Mon, 11 Jul 2005 00:52:37 -0500
Hm, the plot thickens. Well, how about a breakpoint on [NSCFArray
size], and seeing where it's getting called? What do you mean by
"gets really weird" ?
On Jul 11, 2005, at 12:45 AM, Matt Ball wrote:
When I change shadowedImageWithImage to return what it receives, the
tableView works as expected for two or three clicks, and then it gets
really weird, and I get this in my log:
-[NSCFArray size]: selector not recognized [self = 0x327550]
- Matt Ball
On 7/11/05, Charilaos Skiadas <email@hidden> wrote:
On Jul 11, 2005, at 12:29 AM, Matt Ball wrote:
Oh, and it's not a problem with there being so many objects
added/released. I commented out the mouse tracking code, and the
problem still exists.
I don't see where the problem is then. What if you simplify
shadow.. to just
immediately return what was given to it? What if you work with a
smaller
number of rows, say 3?
Unless someone has a better idea, I would suggest trying to create
a minimal
test case and then submitting a bug. Either it will be a bug, or
you will
figure out the problem trying to create the test case.
- Matt Ball
Haris
Haris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden