Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Memory(?) issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Memory(?) issue

Subject: Memory(?) issue
From: Jacob Bandes-Storch <email@hidden>
Date: Tue, 5 Feb 2008 09:21:47 -0800

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


Follow-Ups:

Re: Memory(?) issue
From: John Stiles <email@hidden>
Re: Memory(?) issue
From: "Kyle Sluder" <email@hidden>


Prev by Date:
Re: receiving a file on app startup

Next by Date:
Re: Can a Controller to accept key down event?

Previous by thread:
Re: CoreData: Can't modify an immutable model

Next by thread:
Re: Memory(?) issue

Index(es):

Date
Thread