Re: Why does this leak memory?
Re: Why does this leak memory?
- Subject: Re: Why does this leak memory?
- From: Matt Ball <email@hidden>
- Date: Mon, 11 Jul 2005 01:48:37 -0400
Oh, and in addition: If I change it so that it resizes the image and
then returns resizedImage, it works fine. I think the weird error is
because the unresized-image is larger than the table row, so it messes
things up. However, when I return [resizedImage autorelease]; instead
of return resizedImage;, I get the same crash we were dealing with
before...
- Matt Ball
On 7/11/05, Matt Ball <email@hidden> 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
> >
> >
> >
>
_______________________________________________
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