Re: Process (Xcode): 68 leaks for 3312 total leaked bytes.
Re: Process (Xcode): 68 leaks for 3312 total leaked bytes.
- Subject: Re: Process (Xcode): 68 leaks for 3312 total leaked bytes.
- From: j o a r <email@hidden>
- Date: Thu, 6 Nov 2008 08:22:38 -0800
On Nov 6, 2008, at 1:25 AM, Tom Bernard wrote:
$ leaks 192
Process 192: 140682 nodes malloced for 10482 KB
Process 192: 68 leaks for 3312 total leaked bytes.
...
This is immediately after launching Xcode shortly after power-up, no
projects open.
Is this typical?
If this sample is indeed taken right after starting Xcode, then per
definition it probably have to be considered typical... Memory leaks
is never a problem caused by the user, always an indication of a
problem in the software product.
That said, as a result of the development tools and technologies used
in the industry today, I think that it's fair to say that all software
have memory leaks. Some have less, some have more. Larger software
products will have more leaks, simply because they contain more code.
With this in mind, finding 68 leaks in Xcode, and with no indication
that they have any other negative side effects, is not that big of a
deal. Should these leaks still be hunted down and fixed? Absolutely,
no doubt about that.
Finally, Xcode is a garbage collected application nowadays (not sure
which version you're using). The definition of what constitutes a
memory leak is for the most part different between reference counted
applications and garbage collected applications. In the former you
typically refer to unreachable memory, and in the latter "unwanted
subgraphs". While you can run the "leaks" command line tool on garbage
collected applications, it's much less useful, and the interpretation
of the results much more difficult.
j o a r
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden