On Apr 30, 2017, at 4:02 PM, Peter Hudson wrote:
>
> Thanks Ken.
>
> I'll give zombies a go.
> What's baffling is that the pointer has remained the same - in terms of
> address - but the type of underlying object appears to be different.
> Not sure how that could happen.
There's a memory m
Thanks Ken.
I'll give zombies a go.
What's baffling is that the pointer has remained the same - in terms of address
- but the type of underlying object appears to be different.
Not sure how that could happen.
Peter
> On 30 Apr 2017, at 21:28, Ken Thomases wrote:
>
>> On Apr 30, 2017, at 2
On Apr 30, 2017, at 2:50 PM, Peter Hudson wrote:
>
> Rather too much code to post it.
> Was wondering about methods to watch particular addresses of memory.
Run the app under the Zombies template of Instruments. The table view, rather
than being deallocated and having its address reused for s
> On Apr 30, 2017, at 14:50, Peter Hudson wrote:
>
> Rather too much code to post it.
> Was wondering about methods to watch particular addresses of memory.
I'd look more at the xib's connections to properties and make sure those
properties have the correct weak/strong decoration.
Steve via
Hi Steve
Rather too much code to post it.
Was wondering about methods to watch particular addresses of memory.
Peter
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
> On Apr 30, 2017, at 08:37, Peter Hudson wrote:
>
> I have a strange memory problem.
>
> My app is a typical document based app.
>
> I have one method which checks on the indexes of selected rows in a table
> view frequently.
>
> After this method has been called ( without a problem ) many
Hi all
I have a strange memory problem.
My app is a typical document based app.
I have one method which checks on the indexes of selected rows in a table view
frequently.
After this method has been called ( without a problem ) many times,
the app grinds to a halt - and points the finger at t
