• 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: Strange Memory leak
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange Memory leak


  • Subject: Re: Strange Memory leak
  • From: Jerrod Fowkes <email@hidden>
  • Date: Tue, 16 May 2006 13:38:14 -0700 (PDT)

j o a r <email@hidden> wrote: Tracking retain count is not an effective way to find memory leaks,
or other memory management problems. You should only care about
keeping your end of the Cocoa memory management agreement - ie.
basically keep retain and release balanced. Don't spend time on
peeking at things that are implementation details of the frameworks
that you use.


There are tools and techniques that are better suited for finding
memory leaks in an structured and effective way:


ManagingMemory/Articles/FindingLeaks.html>

In particular, I like the "leaks" command line utility.


I'm not sure how easy they would be to find, but there are also a lot
of threads on this topic in the list archives:




j o a r


Well for the most part I have kept things tidy. What throws a red flag in this case is that the result is about 1 - 2 meg. After so many calls the Mac OS X is brought to it's knees. The tools would be handy, however when it comes down to it, I have an object with a retain count too high, and it must be released so that I can get my 1-2 meg back. Also in this case It's a good thing that I did come across it with this particular API call. I doubt those tools would have been able to tell me that. I could be wrong though. I haven't found anything in the documentation about it messing around with the clientContext.

I don't know, but it's a possibility that this could help:

I have a loop that runs x Times. in that loop I make a call to a web service and it returns a result of 1-2 meg. So whenver it calls my delegate the CFDictionaryRef outRef actually has a retain count of 2. I have no idea why the heck it would have an extra retain count. I am certainly not retaining it for anything, and by the time it's all said and done with the call it's up to 3. Which doesn't make sense. -Jerrod


---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2ยข/min or less.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Strange Memory leak
      • From: j o a r <email@hidden>
References: 
 >Re: Strange Memory leak (From: j o a r <email@hidden>)

  • Prev by Date: Re: questions: 1: how do I select tableView row? 2: launching app with path
  • Next by Date: Re: More Mac like handling of OS raised exceptions
  • Previous by thread: Re: Strange Memory leak
  • Next by thread: Re: Strange Memory leak
  • Index(es):
    • Date
    • Thread