Hi, We check for leaks before each release but it's possible there's something unique about your setup that's exposing a memory problem. If you go to Terminal and type "leaks Spanning\ Sync" then you can see how much the program has leaked. Keep in mind there will always be some leaks because a) the various Apple frameworks have (usually small) leaks and b) the leaks program doesn't understand certain kinds of memory allocations. Also, the reported number is the number of *bytes*. Divide that by 1024 to get the number of K, and divide that by 1024 to get MB. If it's more than 20K or so, I'd be interested in working with you to track it down.
Thanks -- Larry Hendricks [EMAIL PROTECTED] http://spanningsync.com On Sep 28, 6:26 pm, cvkline <[EMAIL PROTECTED]> wrote: > After rebooting my machine, I've been watching it grow and it looks > like it picks up about 100 megabytes of main memory a day. > > On Sep 27, 11:14 am, cvkline <[EMAIL PROTECTED]> wrote: > > > I just noticed my machine is using a lot more main memory than I > > thought it should. I was a little horrified to discover that > > SpanningSync is taking up nearly a gigabyte of real memory! Surely it > > doesn't need this much to do its job; I suspect there is a memory leak > > in the code somewhere. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Spanning Sync" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/spanningsync?hl=en -~----------~----~----~----~------~----~------~--~---
