[Sparkle] Check updates in background and autorelease

Andy Matuschak andy at andymatuschak.org
Thu May 8 01:41:32 PDT 2008


Ooh, good catch. Revision 155 should fix that.

- Andy Matuschak

On May 8, 2008, at 1:27 AM, Pierre Chatelier wrote:

> Hello,
>
> Since r154, I do the following to check for updates in background :
>
> -(void) applicationDiDFinishLaunching
> ...
>  if ([[NSUserDefaults standardUserDefaults]  
> boolForKey:SUEnableAutomaticChecksKey])
>    [sparkleUpdater checkForUpdatesWithDriver: 
> [[[SUProbingUpdateDriver alloc] init] autorelease]];
> ...
>
> But the console reports :
>
> 08/05/08 10:23:20 LaTeXiT[7084] An instance 0x15b1bd20 of class  
> SUProbingUpdateDriver is being deallocated while key value observers  
> are still registered with it. Observation info is being leaked, and  
> may even become mistakenly attached to some other object. Set a  
> breakpoint on NSKVODeallocateBreak to stop here in the debugger.  
> Here's the current observation info:
> <NSKeyValueObservationInfo 0x15b110b0> (
> <NSKeyValueObservance 0x15b16000: Observer: 0x14e980, Key path:  
> finished, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0,  
> Property: 0x15b15fe0>
> )
>
> Is there a workaround ?
>
> Regards,
>
> Pierre Chatelier
>
> _______________________________________________
> Sparkle mailing list
> Sparkle at lists.andymatuschak.org
> http://lists.andymatuschak.org/listinfo.cgi/sparkle-andymatuschak.org



More information about the Sparkle mailing list