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: Tom Bernard <email@hidden>
- Date: Mon, 10 Nov 2008 03:42:39 -0700
- Thread-topic: Process (Xcode): 68 leaks for 3312 total leaked bytes.
So I probably have better things to do than worry about this. :) Thanks for
the info.
Tom Bernard
email@hidden
on 11/10/08 1:03 AM, Bill Bumgarner at email@hidden wrote:
> Sort of. GCC implements its own memory management scheme
> internally. It is sort of garbage collected, but not anything like
> the Objective-C collector. GCC and the linker are both designed to
> be run once and then quit. In this situation, leaks are largely
> irrelevant beyond keeping the working set small during operation.
>
> From your original message:
>>>> Process 192: 140682 nodes malloced for 10482 KB
>>>> Process 192: 68 leaks for 3312 total leaked bytes.
>
> First, as others have noted, Xcode is a GC'd apps and leaks doesn't
> really work against such apps without very carefully controlling the
> state of the app (which isn't possible at startup). As well, there
> are a handful of blocks that are allocated during app startup for whom
> their pointers will effectively be lost to leaks -- stuck off in
> thread metadata, munged a bit so leaks no longer sees them, or
> otherwise stored in a way that leaks doesn't see it.
>
> In any case, 3K leaked at startup -- some [often most] of which isn't
> really leaks -- is pretty close to irrelevant. It is small, only
> happens once, and is extremely unlikely to contribute to heap
> fragmentation.
>
> The leaks that matter -- the ones that kill performance -- are leaks
> during repeated operations. For example, if Xcode were to leak 4k
> (one page) of memory every time a file is compiled, a file is opened/
> closed, or a search is performed, it will definitely be a real drag on
> performance over time. Beyond consuming memory, such leaks often lead
> to heap fragmentation which causes general VM bloat.
_______________________________________________
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