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: Sun, 10 Jul 2005 22:50:57 -0400
I have to click back in my window because the crash only occurs when I
click on an existing row - not when adding rows or creating the
initial row. Also, each method that is in question right now is called
when the cell refreshes, so changing the location of the breakpoint
doesn't fix the problem.
I've put an NSLog at the beginning and end of each method in question,
and the crash seems to be occurring in the setImage: method. "Begin
setImage" logs, but "End setImage" doesn't.
On 7/10/05, Charilaos Skiadas <email@hidden> wrote:
>
> On Jul 10, 2005, at 9:34 PM, Matt Ball wrote:
>
>
> I've put breakpoints in, but it's causing a lot of trouble. Since
> thecrashing code gets called whenever the cell needs to redraw, it
> messessome things up. I put a breakpoint in, and it gets flagged in
> thedebugger, so I walk it through. Then, when I click back in my window,the
> breakpoint gets flagged again since the cell redraws. It's aconstant loop
> until I terminate the application...
>
> Well, ok, I guess that method has no problem then, since it does not crash
> :-)
> Then remove the breakpoint from that method.
> The point is that we need to figure out which one of your methods gets
> called right before the app crashes.
> What i like doing, not sure if it is the most efficient hting or not, is to
> put an NSLog at the entry and exit of every method I have, stating the name
> of hte method and whether it is entering or exiting. It might help you
> pinpoint the problem a bit more.
>
> Why do you click back in your window?
> Does your app crash just when you start it up, or do you have to do
> something to the UI before it does?
>
>
> - 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