On Jun 20, 2010, at 7:42 AM, unixo wrote: > In my coredata application, I noticed a weird behavior when closing document > windows; to be sure this was not related with some memory leaks introduced by > me, I created a new document-based coredata project, without adding any kind > of customization. > > I did the following test, even if it's not a scientific approach: > - I run the application, then launched Activity Monitor and filtered by this > application name; > - I created a lot of new documents and closed them all. > > I noticed that, after closing all the documents, real memory occupation > increased compared to the startup; I did the previous two steps again, and > memory occupation increased a little bit more. > > Is it normal that this kind of application (coredata) does this way?
Maybe. Did you try running it in Instruments using the object alloc & leaks instruments? For various reasons, Activity Monitor is a poor memory debugging tool. Instruments, OTOH, will show you what is really going on. Nick Zitzmann <http://www.chronosnet.com/> _______________________________________________ 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
