Technology Kills Deconstructing technology, one piece at a time…

SugarSync Memory Leak

First, a quick update about my other major SugarSync issues--SharpCast assisted me in resolving the issue on my laptop in which I had to re-import the previous configuration and re-scan everything each time SugarSync started. That was resolved by uninstalling, reinstalling, then not choosing to import my existing configuration, but instead starting a new one.

I still have major issues with the way it's handling syncing my files, however--every day there are tens or hundreds of files supposedly in sync which are renamed inexplicably whenever I try to save them. Deleted folders still reappear if I do not permanently delete them manually from SugarSync. Some files still never sync, even though SugarSync indicates all files are "backed up and in sync." Hopefully they are still looking into these other issues as well.

Now, a new issue. For the past several weeks, I have been dealing with my Windows 7 Professional x64 machine's 4 GB of RAM filling up within a day or two of leaving it running. No listed application was actually using that RAM--adding up the reported memory commits of all running processes did not equal the amount of RAM which was used up. So I knew I was dealing with some sort of memory leak.

I tried disabling things I didn't necessarily need, but nothing helped until I finally decided to disable SugarSync from starting. Even though it would report very small memory usage, my memory leaks stopped completely when I stopped running SugarSync all the time. Looking at the process's history it would regularly use ~500 MB or more, but nowhere near what was actually being used on my system.

I do not have this issue on my Windows XP laptop, so it seems to be related to SugarSync and Windows 7 (not sure about Vista).

Anyone else noticed such behavior? I will report it to SharpCast so they can investigate further--maybe it's not SugarSync specifically but some interaction between SugarSync and another process running. But it makes my system crawl when the memory usage reaches 90 or 95% and the only resolution is a restart, so for the time being I am no longer running SS.