• 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: "Sean McBride" <email@hidden>
  • Date: Fri, 30 May 2008 12:24:40 -0400
  • Organization: Rogue Research

On 5/24/08 10:42 AM, Bill Bumgarner said:

>Probably not.   The tools aren't generally designed to capture the
>state of an application when it closes because memory leaks at that
>point in time are generally completely irrelevant;  the system will
>reclaim the memory of an application when it quits in its entirety.
>
>However, there are cases where you might need to know.  For example,
>testing for memory leaks at the end of a unit test run is often a
>great way to find leaks in framework code.

For OCUnit, would -(void)tearDown be the right place to test for leaks?

--
____________________________________________________________
Sean McBride, B. Eng                 email@hidden
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada

 _______________________________________________
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>)

  • Prev by Date: Re: IB 3.1: sliding an object from the libr pallet onto the xib wk area vs onto a host view...
  • Next by Date: What?
  • Previous by thread: Re: Memory Leak
  • Next by thread: Re: Memory Leak
  • Index(es):
    • Date
    • Thread