Re: Cocoa Memory Leaks
Re: Cocoa Memory Leaks
- Subject: Re: Cocoa Memory Leaks
- From: j o a r <email@hidden>
- Date: Tue, 21 Jun 2005 07:57:26 +0200
On 21 jun 2005, at 01.29, Dominic Feira wrote:
I am in the process of hunting down some memory leaks and seem to
have come across a leak.
Here is some output from ObjectAlloc (which can't be copied from,
ugh):
70 [NSTableView drawRect:]
70 [NSTableView drawRow: clipRect:]
37 [NSTextFieldCell drawWithFrame: inView:]
33 [NSActionCell setObjectValue:]
I'll spare you the complete dump. Anyway, if you follow both
drawWithFrame: inView and setObjectValue: all the way down to the
leaf nodes, there is a CFStringCreateCopy that is creating all of
the CFString immutables. None of these seem to ever bee freed.
Are you sure that the leaks are in Cocoa, and not in your code? Check
your table view data source! A leak in that part of Cocoa is in my
opinion a bit unlikely, as that code path is called so often that if
it were a regression even for 10.3.9, I think it should have been
identified sooner than this. I could of course be wrong though.
Can you isolate this problem into a small sample project and post it
online for us to have a look?
Is this a known issue (I'm developing on 10.3.9)?
Not that I know of - but as I don't work for Apple, I can't say for
sure.
How many other leaks are there in Cocoa?
There are exactly 17 other leaks in Cocoa. No, I'm just kidding.
Seriously dude - what kind of question is that? ;-)
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden