Comments for Naren

Comment on Running NSTimer on Separate Thread by Hasnat

Hasnat — Mon, 23 Nov 2009 11:22:27 +0000

incase you are wondering how to stop it
just use
[timer invalidate];
in timerTick:

Comment on Running NSTimer on Separate Thread by Rorun

Rorun — Thu, 27 Aug 2009 16:10:51 +0000

Hi!, I newbie in the manage of threads in COCOA. In the example, How kill the thread? if I need use many threads, and i need kill each one of them. What is the correct way for manipulate them.

Thanks.

Comment on Running NSTimer on Separate Thread by narendra.tumkur

narendra.tumkur — Mon, 27 Jul 2009 06:58:29 +0000

No problem. Glad I could help.

Comment on Running NSTimer on Separate Thread by rebs

rebs — Sun, 26 Jul 2009 23:22:19 +0000

Hey just wanted to say thanks, I was hitting my head against the brick wall with the problem of the thread exiting.

the [runLoop run] fixed it!.

Comment on Running NSTimer on Separate Thread by narendra.tumkur

narendra.tumkur — Sun, 05 Jul 2009 14:15:11 +0000

Hey Handi,
I’m not sure why there is a leak. I haven’t had time to try it out myself.
You can however find out which object has not been released with the Leak performance tool.
Sorry I can’t be of much help right now

Cheers
Naren

Comment on Running NSTimer on Separate Thread by Handi

Handi — Thu, 02 Jul 2009 15:02:16 +0000

Hi Naren,

I just tried that too and it is still leaking the same thing.
This is what being shown in the tool:
Leaked Object # Address Size Responsible Library Responsible Frame
Malloc 16 Bytes 0×3a19f70 16 WebCore CurrentThreadContext()

Thx for such prompt reply!

Handi

Comment on Running NSTimer on Separate Thread by narendra.tumkur

narendra.tumkur — Thu, 02 Jul 2009 04:32:08 +0000

Hi Handi,
I am not able to check this immediately, but is it possible that you need to do a [NSTimer release] before [pool release]?

Naren

Comment on Running NSTimer on Separate Thread by Handi

Handi — Thu, 02 Jul 2009 03:14:21 +0000

Hi Naren,

Thank you for writing this example.
I did the same thing but I ran into a leak problem on the runloop.
I ran “Leak” performance tool on my app. And it always pointing out that I have a 16 bytes leak on [runloop run].
This leak only happens after I have the timer finish running meaning the timer got invalidated -> [pool release] got called.

I wonder if you are having the same issue as well.

I read in the documentation that NSRunLoop should only be called within the context of current thread. I wonder if this is causing the leak…

Handi