On 2010 Feb 07, at 08:58, Matt Neuburg wrote:
> the fact that it is *still* after all these years of Cocoa
> impossible to ask an NSNotificationCenter to display its dispatch table, for
> debugging purposes, is simply inhuman. I've had a bug in on this for years,
> which remains open. m.
Maybe y
On Fri, 5 Feb 2010 13:04:06 -0800 (PST), Keith Blount
said:
>in its nib somewhere internally, but it *is* getting released after all. The
problem is that during 3), the project that is loading sends out some
notifications while the array controller is still around, so the array
controller still i
; From: Graham Cox
> Subject: Re: Debugging (apparently) random retain loop bug (NSArrayController)
> To: "Keith Blount"
> Cc: cocoa-dev@lists.apple.com
> Date: Friday, February 5, 2010, 1:11 AM
>
> On 05/02/2010, at 11:41 AM, Keith Blount wrote:
>
> > Many than
On Fri, 5 Feb 2010 12:11:18 +1100, Graham Cox said:
>
>Unfortunately it is a bugger to track down 'who is retaining me' and as far as
I know there isn't much to help out with that.
Why not use Instruments? You can record reference counts, and then every
retain / release for every object can be ex
On 05/02/2010, at 11:41 AM, Keith Blount wrote:
> Many thanks for the reply, much appreciated. The strange thing with this one
> is that I've been through the code in all the obvious places and I can't find
> that it's been retained anywhere. It's an NSArrayController subclass that is
> only r
in this situation in the hope of finding the underlying
problem (fortunately this is in a beta version of the next version of the
product rather than in the official release version).
Thanks again and all the best,
Keith
--- On Thu, 2/4/10, Graham Cox wrote:
> From: Graham Cox
> Subject
On 05/02/2010, at 7:21 AM, Keith Blount wrote:
> Occasionally, if you close a document (NSDocument subclass) in my app and
> then open another document (or reopen the same document), the app crashes.
> I've debugged this to the extent that I now know the cause, at least. What is
> happening is
Hello,
For several months now I've been trying to track down a particular bug that can
cause a crash in my app, and finally I figured I would cry for help in case
there is anything obvious that I can try that I'm not already trying. Here's
the situation:
Occasionally, if you close a document (
