Re: Memory(?) issue
Re: Memory(?) issue
- Subject: Re: Memory(?) issue
- From: John Stiles <email@hidden>
- Date: Tue, 05 Feb 2008 09:41:36 -0800
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