Re: how worried should I be about these console messages?
Re: how worried should I be about these console messages?
- Subject: Re: how worried should I be about these console messages?
- From: Chris Espinosa <email@hidden>
- Date: Wed, 7 Nov 2007 13:06:30 -0800
On Nov 7, 2007, at 12:52 PM, Joe Davison wrote: On 7 Nov 2007, at 12:47, email@hidden wrote:
On 7 Nov 2007, at 19:42, Chris Espinosa wrote:
The second one is an error deep in some system framework when running under Garbage Collection that we have not been able to track down yet. It simply means that somebody has neglected to do a final release on a memory block that nobody has kept a pointer to (making the final release technically impossible). The Garbage Collector knows the block is inaccessible and is freeing it, but is warning us that somebody forgot to formally release it before the pointer to it went out of scope. Bad form, but no actual harm.
So if you guys are having trouble tracking down such issues with GC, how hard is it going to be for the rest of us ;)
Well, as one who comes from a Lisp / Smalltalk background, what sounds strange to me is that someone has to formally release it, instead of having the GC recognize it's no longer needed and silently recycle it.
Objective-C 2.0's automatic garbage collection is indeed automatic, but you can write framework code that can run either GC or non-GC. To do so it still has to do retain/release so that non-GC clients work correctly. Xcode, running under GC, is simply pointing out that a non-GC app would experience a leak in the framework at that point, but because it's using GC, it's not.
Chris |
_______________________________________________
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