• 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: Quincey Morris <email@hidden>
  • Date: Fri, 04 Sep 2015 00:21:03 +0000

Two thoughts about this.

1. Are you sure that ‘updateTime’ is running on the main thread? It needs to be, since you’re updating the UI directly from this code.

2. The code inside ‘updateTime’ is very self-contained, so it seems easy to try a divide-and-conquer strategy. What happens if you remove all the code, so that the method consists of empty braces? What happens if you don’t format anything, but simply set the UILabel fields to a constant string each time?

My guess is that the problem will persist regardless of what the method does, and the problem is elsewhere. But at least it would be useful to rule this method’s code out, if you can.


_______________________________________________

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: Re: Puzzling memory creep
  • Next by Date: Re: Puzzling memory creep
  • Previous by thread: Re: Puzzling memory creep
  • Next by thread: Re: Puzzling memory creep
  • Index(es):
    • Date
    • Thread