• 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(?) issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory(?) issue


  • Subject: Re: Memory(?) issue
  • From: John Stiles <email@hidden>
  • Date: Wed, 06 Feb 2008 19:15:53 -0800

ObjectAlloc can tell you that.
Or I think Instruments can too, if you're in Leopard.

Jacob Bandes-Storch wrote:
How do I figure out what the objects are that were allocated? It's hard to debug when all I know is which method was called...

On Feb 5, 2008, at 9:41 AM, John Stiles wrote:

You could use MallocDebug to show you where all the allocations are coming from, if the problem really is allocations.

Allocations aren't considered leaks if you are holding on to a pointer to them, so "leaks" won't find a lot of simple problems (like if your code is accidentally growing an array or dictionary larger and larger and larger without ever shrinking it back down).


Jacob Bandes-Storch wrote:
When my application has been running for a few minutes, Expose starts being jerky. My app takes almost 0 CPU. However, its real and virtual memory usage keeps increasing. I used Instruments to check for leaks and eliminated all of them. When I run leaks, the output is something like this:

Process 327: 16547 nodes malloced for 2067 KB
Process 327: 0 leaks for 0 total leaked bytes.

When I quit my app, Expose starts working normally again. Yesterday I left the program running all day, and came back to my computer being at the login screen; I tried to log in again and it froze. After restarting, the console was full of these messages:

kernel     proc: table is full

Is this a memory issue or something else? How can I accurately debug this?
_______________________________________________


Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Memory(?) issue
      • From: j o a r <email@hidden>
References: 
 >Memory(?) issue (From: Jacob Bandes-Storch <email@hidden>)
 >Re: Memory(?) issue (From: John Stiles <email@hidden>)
 >Re: Memory(?) issue (From: Jacob Bandes-Storch <email@hidden>)

  • Prev by Date: Re: Memory(?) issue
  • Next by Date: Re: Use of Mac OS X 10.5 / Leopards Garbage Collection Considered Harmful
  • Previous by thread: Re: Memory(?) issue
  • Next by thread: Re: Memory(?) issue
  • Index(es):
    • Date
    • Thread