• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Puzzling memory creep
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Puzzling memory creep


  • Subject: Re: Puzzling memory creep
  • From: Scott Ribe <email@hidden>
  • Date: Thu, 03 Sep 2015 18:11:42 -0600

On Aug 14, 2015, at 2:29 PM, Richard Kennaway <email@hidden> wrote:
>
> the Responsible Caller is _dispatch_continuation_alloc_from_heap

Sure sounds like something that *might* underly the implementation of NSTimer.

Quick experiment: change the delay in your NSTimer creation from 1.0 to 0.1 and see what happens to memory usage ;-)

Also, you are aware that you can get the full stack trace for any allocation, right? (You may have to set an option in the instrument before you start the run, I don't remember.)

--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice






_______________________________________________

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


  • Follow-Ups:
    • Re: Puzzling memory creep
      • From: Richard Kennaway <email@hidden>
References: 
 >Puzzling memory creep (From: Richard Kennaway <email@hidden>)

  • Prev by Date: Forcing an NSScroller to think its scroll document has a different width. Possible?
  • Next by Date: Re: Puzzling memory creep
  • Previous by thread: Puzzling memory creep
  • Next by thread: Re: Puzzling memory creep
  • Index(es):
    • Date
    • Thread