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: Joe Davison <email@hidden>
- Date: Wed, 7 Nov 2007 14:52:04 -0600
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 ;)
Matt Gough
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.
Actually, I've not really gotten into ObjC yet, basically because I
hadn't wanted to spend the energy to really understand the memory
management issues. I'm glad to hear there's a new GC regime in ObjC,
and I'm looking forward to it. I guess it's still not fully
automatic though. Still, gotta beat C/C++ eh?
joe
_______________________________________________
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