[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: trying to debug problems with NSAutoreleasepool

From: Sebastian Reitenbach
Subject: Re: trying to debug problems with NSAutoreleasepool
Date: Wed, 28 Nov 2007 20:45:40 +0100


Richard Frith-Macdonald <address@hidden> wrote: 
> On 2007-11-27 16:40:36 +0000 "Sebastian Reitenbach" 
> <address@hidden> wrote:

> > At least at ten places in opengroupware I commented out a [pool 
> > release]; or 
> > equivalent, to prevent these crashers.
> > 
> > As I doubt, that commenting out these lines, is the right solution,
> Almost certainly not ... that probably introduces a big memory leak.
> Most likely you have a problem with objects being released more times 
> than they are retained.
> You can call [NSObject enableDoubleReleaseCheck: YES]; to turn on some 
> checking for this ... but it will slow down your code quite a bit.
I added that enableDoubleReleaseCheck directly in the method, after the 
allocation of the NSAutoreleasepool, but that ended in an exception. 
Where would be the correct place to enable that?

> You can set the environment variable NSZombieEnabled to YES ... which 
> will give you diagnostics about any attempt to use a deallocated 
> object, but will use lots of memory.
> You can also set NSDeallocateZombies to YES to avoid leaking memory as 
> zombie objects, but this will give you less informative and less 
> reliable (the memory from a deallocated object could have been re-used 
> as another object) logging.
I set these environment variables, and also started the 
ogo-webui-1.1 -NSDebugEnabled YES -NSZombieEnabled YES -NSDeallocateZombies 
YES -WOUseWatchDog NO
I searched a bit around, and found this:
I also explicitly #include <Foundation/NSDebug.h>

but I did not observed any changes? 
What should I expect to see with these enabled?

kind regards

reply via email to

[Prev in Thread] Current Thread [Next in Thread]