Ok, fair enough: http://sourceforge.net/svn/?group_id=188286
I'm also using another framework in there, which I suspect might be the culprit, however (because MallocDebug reports just 56 bytes leaked)...but thanks for any insight you can provide.
Paul
----------Original Message----------
On 3/3/07 12:57 , Bill Bumgarner (email@hidden) wrote:
> On Mar 3, 2007, at 12:50 PM, Paul Borokhov wrote:
>>> It appears that NSLock is leaking memory ... This is also happening
>>> to a lesser extent with CFBag, CFRunLoopSource, and NSRecursiveLock.
>>> I'm not using any of these in my code directly ...
>
> Right -- those classes don't leak on their own. You are doing
> something to cause the leaks. So, to answer your question, the list
> is going to need more context... going to need at least some of your
> code or a much better description of exactly how you are allocating
> and managing the various instances.
>
> b.bum
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
