On Jul 8, 2007, at 20:03, Justin C. Walker wrote: > > On Jul 8, 2007, at 19:42 , Fernando Pereira wrote: > >> I noticed that BibDesk was using over 200MB of real memory with a >> single small (18 entries) bibliography loaded; it had been open for >> several days. Exiting BibBesk and reopening the file brought that >> down to 19MB. > > Hadn't noticed, but this prompted me to poke around a bit: previewing > seems to have no lingering effect on memory, but opening an edit > window bumps memory by 1.5MB. Closing it drops memory by 1.0 MB, > with an apparent leak of .5MB. Could be cacheing or other effects > here, since I didn't do any serious/long-term checking.
The editor window is a resource hog, but I don't see any obvious leaks in it, so you're likely seeing some caching, as you say. Running leaks/MallocDebug/OmniObjectMeter or similar tools is the most reliable way to find leaks, although Activity Monitor is useful in case of gross leakage. For instance, one thing we do is cache all strings for autocompletion when editing, and those stay around after the document closes. In Activity Monitor, this looks like a leak, but it's a red herring (as many of you are likely aware anyway :). -- Adam ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
