Re: Cocoa-dev Digest, Vol 6, Issue 1051
Re: Cocoa-dev Digest, Vol 6, Issue 1051
- Subject: Re: Cocoa-dev Digest, Vol 6, Issue 1051
- From: Karl Moskowski <email@hidden>
- Date: Wed, 22 Jul 2009 15:17:26 -0400
On Jul 22, 2009, at 10:30 AM, Tarek Khouzam wrote:
So here is my issue. I have an app that when it should have hit the
limit of memory it needs to use, it keeps growing over time.
But after 12 hours or so its memory grows about 10x. So what I would
like to know is where I should go from here? GC should be taking
care of freeing unneeded memory. I can't use the old apps like leaks
because its not valid anymore. Is there a technique or app that can
show me what object is using all the memory
?
Basically I am at wits end. I have tried Instruments but I have a
better chance of reading Chinese then understanding what Instruments
is tell me. Any help would be greatly appreciated.
I had a similar problem a few months ago. This thread may help:
<http://www.cocoabuilder.com/archive/message/cocoa/2009/3/12/232167>
On Leopard at least, it seems that when nothing happens in the UI
thread, the collector never kicks in. The workaround was to do
something in the UI - click a menu, resize a window, etc. When I was
further along in development and added a progress bar that was updated
frequently, the symptom disappeared.
----
Karl Moskowski <email@hidden>
Voodoo Ergonomics Inc. <http://voodooergonomics.com/>
_______________________________________________
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