thanks ken for all the input. i will work on the things you've mentioned. i
really appreciate it!
rick
From: Ken Thomases
To: Rick C.
Cc: cocoa dev
Sent: Saturday, October 3, 2009 10:37:11 PM
Subject: Re: memory advice for still learning coder
Oh
Oh, and I forgot to respond to this:
On Oct 3, 2009, at 9:17 AM, Rick C. wrote:
4. i don't believe i'm having a problem with the arrays being
accessed the same time by different threads. although i am not
using a lock.
If I'm understanding what you're saying, you're courting disaster. I
On Oct 3, 2009, at 9:17 AM, Rick C. wrote:
5. returning i am not doing. :-( maybe a bad error on my part. in
the thread method my first line i alloc/init an autorelease pool and
the last line i release the pool. should my last line be return?
the method is void.
Allowing the method t
y using a timer but it didn't quite cut it. thanks
again,
rick
From: Ken Thomases
To: Rick C.
Cc: cocoa dev
Sent: Saturday, October 3, 2009 7:15:13 PM
Subject: Re: memory advice for still learning coder
On Oct 3, 2009, at 2:38 AM, Rick C. wrote:
&
On Oct 3, 2009, at 2:38 AM, Rick C. wrote:
i'm having a few memory issues where my memory climbs over time
although using leaks it shows i have no leaks.
Leaks aren't the only way to use excessive memory. For example, if
you keep allocating objects and putting them in a collection somewher
hello,
i'm having a few memory issues where my memory climbs over time although using
leaks it shows i have no leaks. i have gone over my code many times making
sure i release items that need it and have gone over the docs looking for
something i might be missing. i'm thinking my problem migh
