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

Re: Memory Leak


  • Subject: Re: Memory Leak
  • From: Marshall Clow <email@hidden>
  • Date: Mon, 26 May 2008 11:10:35 -0700

At 10:39 AM -0400 5/26/08, Sean McBride wrote:
On 5/24/08 10:42 AM, Bill Bumgarner said:
I disagree with your assessment.  I would love to see such a feature in
Xcode.  Finding leaks with Instrument/MallocDebug/leaks requires
breaking one's workflow.  If Xcode printed leaks after every run, it
would be easier to find leaks _right away_ instead of weeks later when
one decides to run it through a special tool.  Yes, the OS will clean
everything up, but if execution reaches the end of main() and memory is
still hanging around, there is no doubt that it is a leak.  That's a
great time to check for leaks.

I agree with Bill. The end of the program is a good (the best?) first step in leak detection.
Pick the low hanging fruit.


I do have one minor disagreement. Lots of stuff happens after main () exits. (especially in C++) Destructors for global objects run. A leak detector needs to check after that.
--
-- Marshall


Marshall Clow     Idio Software   <mailto:email@hidden>

It is by caffeine alone I set my mind in motion.
It is by the beans of Java that thoughts acquire speed,
the hands acquire shaking, the shaking becomes a warning.
It is by caffeine alone I set my mind in motion.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Memory Leak (From: Romain Marucchi <email@hidden>)
 >Re: Memory Leak (From: Bill Bumgarner <email@hidden>)
 >Re: Memory Leak (From: "Sean McBride" <email@hidden>)

  • Prev by Date: Re: Problems Building Apple's CryptoSample
  • Next by Date: Re: Memory Leak
  • Previous by thread: Re: Memory Leak
  • Next by thread: Re: Memory Leak
  • Index(es):
    • Date
    • Thread