Re: Lost memory, GCD, dispatch sources, Cocoa bindings & User interface
Re: Lost memory, GCD, dispatch sources, Cocoa bindings & User interface
- Subject: Re: Lost memory, GCD, dispatch sources, Cocoa bindings & User interface
- From: Quincey Morris <email@hidden>
- Date: Wed, 16 Sep 2015 16:58:04 +0000
On Sep 16, 2015, at 04:00 , Jean Suisse <email@hidden> wrote:
>
> Does anyone know what to try / measure / observe to get more clues?
It seems you’re “losing” free memory fast enough for this to be visible using heap generations in Instruments’ Allocations. The difficulty with marking generations is that you’d really like the app (at least its memory-wasting activities) to go quiescent long enough and often enough to let you set marks when it’s not doing anything.
You could do this by changing your timer to fire (say) every minute instead of every second. In Instruments, wait until you see a UI update, then wait about 30 more seconds, then mark the generation. Do this several times, and you should be able find out exactly what’s being leaked. (“Why” might be harder.)
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
- Prev by Date:
Re: Lost memory, GCD, dispatch sources, Cocoa bindings & User interface
- Next by Date:
Re: Lost memory, GCD, dispatch sources, Cocoa bindings & User interface
- Previous by thread:
Re: Lost memory, GCD, dispatch sources, Cocoa bindings & User interface
- Next by thread:
Re: Lost memory, GCD, dispatch sources, Cocoa bindings & User interface
- Index(es):