Re: New NSZombie warning on CFRunLoopTimer
Re: New NSZombie warning on CFRunLoopTimer
- Subject: Re: New NSZombie warning on CFRunLoopTimer
- From: Michael Ash <email@hidden>
- Date: Sat, 31 Jan 2009 17:52:22 -0500
On Sat, Jan 31, 2009 at 3:45 PM, Fritz Anderson <email@hidden> wrote:
> SDK 10.4, target 10.3, environment 10.5.6
>
> In the course of startup, my application creates one NSTimer and conducts
> one transaction through the Web Services Core framework (culminating in
> WSMethodInvocationScheduleWithRunLoop).
>
> NSZombieEnabled is YES.
>
> When the scheduled invocation returns with the server's response, I start
> getting this message -- it repeats periodically:
>
> ==
> 2009-01-31 14:15:21.769 MyApp[53942:813] *** -[CFRunLoopTimer _cfTypeID]:
> message sent to deallocated instance 0x15a3bbb0
> ==
>
> There is only one NSTimer I create before this point. Here is the
> print-object of that timer. You see it's not the instance the zombie message
> complains about:
>
> ==
> Printing description of _splashScreenTimer:
> <CFRunLoopTimer 0x1a4550 [0xa03a81a0]>{locked = No, valid = Yes, interval =
> 0, next fire date = 255125688, order = 0, callout = ??? (0x9506cd90),
> context = <CFRunLoopTimer context 0x1ab550>}
> ==
>
> My application appears to run fine. Should I be worried?
Yes. You have a major bug. That it happens to be benign in this
particular case is just an unfortunate coincidence. You should figure
out why this object is being prematurely destroyed and fix it.
Instruments and the malloc debug environment variables can help you
figure it out.
Mike
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden