So...now that threads have been implemented...
It appears that NSLock is leaking memory. My application performs
regular updates and retrieves data every 6 seconds from the web.
Each update is done by a separate method and each method is
detached from the main thread when the timer fires. Now, NSLock
uses continuously more memory as the application runs, according to
ObjectAlloc. This is also happening to a lesser extent with CFBag,
CFRunLoopSource, and NSRecursiveLock. I'm not using any of these in
my code directly so I'm a bit curious as to why they are using
memory, and more and more of it with each minute.
Any ideas?
Paul
Did you implement an NSAutoreleasePool for your threads? Otherwise
any object that will be sent an autorelease method will simply leak
memory.
Good luck, Patrick
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
