Re: Re: memory leaks / finding object references

• Subject: Re: Re: memory leaks / finding object references
• From: "Jason J. Corso" <email@hidden>
• Date: Wed, 30 Aug 2006 08:57:23 -0700
• Delivered-to: email@hidden
• Delivered-to: email@hidden
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=oekTnugIAda0jS7H2HC1UBBpSSdlxFszavdGP74zkOxA8Cm4HtDddKQRuk1Qbs7SlHot00SvbVI9OOrh3BPnjrqNe5X+XK0LyDiQ5QnYdM6SEsD54o1p5C65KY7Pu5c1l3KoE0qQQalYagIzx6sdRrVubRUfidl0Y/69YqKyBJQ=

A free memory/heap profiler with decent functionality is available at
http://jb2works.com/refscan/usage.html.  It allows you to take heap
snapshots and automatically create diffs to analyze.
I've used it only once, but found it to be helpful.

Jason

On Aug 30, 2006, at 7:54 AM, Sciss wrote:
>

> so are there any automatic ways for determining this (getting a
> list of references to object 'myDoc')?
>

Sorry, I didn't look at this closely enough. What I showed would
confirm the Document class as involved in a memory leak and tell you
where the instances are coming from but would not identify
references. You used to be able to do that of sorts with the
classical MacsBug dcmd. I haven't looked into anything recently to
track down references so can't say if hprof or anything else provides
anything or not that would help.

Again apologies for not reading closely enough before posting.

Mike Hall        mikehall at spacestar dot net
http://www.spacestar.net/users/mikehall
http://sourceforge.net/projects/macnative

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden

• Follow-Ups:
  • Re: memory leaks / finding object references
    • From: Sciss <email@hidden>

• Prev by Date: Re: memory leaks / finding object references
• Next by Date: Re: Specifying per-window client properties
• Previous by thread: Re: memory leaks / finding object references
• Next by thread: Re: memory leaks / finding object references
• Index(es):
  • Date
  • Thread