• 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: Report Conflict: Leaks vs. MallocDebug
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Report Conflict: Leaks vs. MallocDebug


  • Subject: Re: Report Conflict: Leaks vs. MallocDebug
  • From: j o a r <email@hidden>
  • Date: Tue, 24 Jan 2006 21:03:52 +0100


On 24 jan 2006, at 20.37, Chris Outwin wrote:

Even when I add an outlet in my NSWindowController subclass to my NSImageView subclass, and include:
- (void)windowWillClose:(NSNotification *)aNotification {
[view release];
}

This is incorrect, unless the view is a top level item in the nib file.

Malloc debug still reports a 12 byte leak. Leaks reports no leak. Could someone please help me?

If you call this method 1.000.000 times, does the memory footprint of your application grow or not?


j o a r


Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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: Report Conflict: Leaks vs. MallocDebug
      • From: Chris Outwin <email@hidden>
References: 
 >Report Conflict: Leaks vs. MallocDebug (From: Chris Outwin <email@hidden>)

  • Prev by Date: Re: Contextual Menu Plug-ins for Universal Binaries
  • Next by Date: Re: Contextual Menu Plug-ins for Universal Binaries
  • Previous by thread: Re: Report Conflict: Leaks vs. MallocDebug
  • Next by thread: Re: Report Conflict: Leaks vs. MallocDebug
  • Index(es):
    • Date
    • Thread