On Oct 3, 2009, at 9:17 AM, Rick C. wrote:
5. returning i am not doing. :-( maybe a bad error on my part. in the thread method my first line i alloc/init an autorelease pool and the last line i release the pool. should my last line be return? the method is void.
Allowing the method to return doesn't require that there's a return statement. I only mean that you allow execution to leave the method back to the caller. As opposed to, for example, leaving it in a permanent loop or blocking call, such that the method (and, thus, the thread) never exits.
at this point it seems my issue is with my threads. i have maybe 4 methods i call by performSelectorinBackground and everytime i use this call i see the memory jump. if i will test all the areas of my project and trigger all the thread calls my memory will jump the most. once i will trigger one thread call even if i will repeat that call in my project the memory will jump to a certain point and that's it. but if i will trigger another thread call the memory will jump again.
If you can trigger a very clear memory jump, that's a perfect candidate for the Object Alloc instrument analysis I described. Select a range covering the jump, have it show only the still-living objects, and those will be the ones accounting for the jump.
Regards, Ken _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
