Fwd: -[NSInvocation length]: selector not recognized [self = 0x30abd0]

  • On 9/23/07, Jim Correia <jim.correia...> wrote:
    >
    > On Sep 23, 2007, at 4:14 PM, NSTask wrote:
    >
    >> NSZombie has returned this.
    >>
    >> Selector 'retain' sent to dealloced instance 0x30ca40 of class
    >> NSInvocation.
    >> Break at '-[_NSZombie retain]' to debug.
    >
    > So an instande of NSInvocation is being used, but has been deallocated.
    >
    > Are you using NSInvocation directly?

    Yes, I am using NSInvocation directly.

    Follow the advice of the logged message, and when you stop look at
    > the backtrace and work backwards to find the memory management bug.

    I backtraced it to see the memory management bug and fixed it. By the time
    object
    reaches to the client it automatically gets released.
    So for testing I retained it again and got this

    [NSConcreteData _fastCharacterContents]: selector not recognized [self =
    0x30d000]

    /S.
previous month september 2007 next month
MTWTFSS
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
Go to today