• 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: Using Fix and Continue with Object Alloc
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using Fix and Continue with Object Alloc


  • Subject: Re: Using Fix and Continue with Object Alloc
  • From: Mike Abdullah <email@hidden>
  • Date: Mon, 15 May 2006 09:30:28 +0100

It's possible that you have two objects who are retaining each other. If this happens they'll "exist" (so ObjectAlloc will see them), but since each is actually being retained, the leaks tool won't find them.

I'm sure there are other situations you could have.

Mike.

On 14 May 2006, at 23:51PM, email@hidden wrote:


On 2006/05/14, at 15:06, email@hidden wrote:


On 2006/05/14, at 14:08, David Dunham wrote:


On 14 May 2006, at 11:59, email@hidden wrote:

Right now, I have an NSDocument based app that is leaking model objects, so in between opening and closing (testing the leak)
documents, I want to try close different paths of execution (to isolate the leak) while monitoring the object count in object alloc, but I cant seem to find a way
to get xcode to do fix and continue, while monitoring in object alloc, and conversely, object alloc doesn't want to attach to a process
stuck in GDB.... any pointers??

Have you tried setting the environment variable MallocStackLogging to 1, and using the command line leaks tool?
Just to follow up. Something strange... when I fire up Object Alloc, and monitor my objects (specifically, NSManagedObjectContext, MyDocument etc.)
they are not released when closing a document... that was the memory leak I found. Yet, when I check using the leak tool (with MallocStackLogging) on the command line,
there are no leaks reported... (except some random apple CFString). This is puzzling... this is also what I noticed using Omni Object Meter (when it wasn't crashing),
there were no leaks detected, but OA did.... is it possible OA is the culprit to my 'leaks?' Is it notorious for doing something like this?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com


This email sent to email@hidden

_______________________________________________ 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
References: 
 >Re: Using Fix and Continue with Object Alloc (From: email@hidden)

  • Prev by Date: Re: NSManagedObjectContext<NSCoding> ?
  • Next by Date: Re: NSManagedObjectContext<NSCoding> ?
  • Previous by thread: Re: Using Fix and Continue with Object Alloc
  • Next by thread: Possible RBSplitView BOF at WWDC
  • Index(es):
    • Date
    • Thread