Bug #514: High ram usage

Comments

1. Greg Hurrell 2006-12-03T07:12:22Z

   Thanks for the report. Can you run the "leaks" command line tool on Synergy when it is running to see if any leaks are reported?

   Just say the pid number of Synergy is 10942 (for example), you would type:

   leaks 10942

   You can look up the pid number of Synergy in the Activity Monitor. After executing the command you should see a list of leaks. In my case, I see:

   Process 10942: 60585 nodes malloced for 8298 KB Process 10942: 153 leaks for 9376 total leaked bytes.

   So it's leaking about 9 kilobytes, that's when it's been running for about 3 days straight. For comparison, I'm seeing 28.43 MB of real memory usage, 269.64 MB virtual.

   I am not sure if you have to have the Xcode Tools installed, or if the "leaks" tool comes installed by default. For more info on "leaks" type this in the terminal:

   man leaks

2. neilio 2006-12-10T13:08:11Z

   Created an attachment (id=87) Leaks output

   Attaching the output from running leaks against Synergy -- when this info was captured Activity Monitor showed Synergy as using up 115mbs of real memory.

3. Greg Hurrell 2006-12-10T14:00:54Z

   Thanks very much for attaching the output, Neil. This confirms that the problem is not any leaks in Synergy.

   How much memory do you have installed in your machine? The way Mac OS X works, the more memory you have, the more memory it will give to each running app. In my case I have 2 GB and Synergy is currently using 23.47MB real, 272.79MB virtual, which is pretty much in line with what I reported in my last comment; at this point the machine has been up for 2 days 10 hours and Synergy (and iTunes) have been running uninterrupted for that whole time).

   It's a little bit hard to collect more information remotely. If you have the Xcode Tools installed you could run the "ObjectAlloc" application (in /Developer/Applications/Performance Tools/) and have a look at what kinds of objects are being allocated.

4. bugzilla user 472 2007-09-19T12:49:50Z

   I'm also having a rather serious memory leak problem. When I start Synergy it uses about 30 megs of RAM, but after a couple of days it is around 200-240 megs. I have the developer tools installed and can run whatever tool on Syngery. My leaks output currently shows the following:

   Process 5872: 701442 nodes malloced for 44682 KB Process 5872: 53 leaks for 3088 total leaked bytes.

   HTH

5. Greg Hurrell 2007-09-19T14:30:52Z

   (In reply to comment #4)

   I'm also having a rather serious memory leak problem. When I start Synergy it uses about 30 megs of RAM, but after a couple of days it is around 200-240 megs. I have the developer tools installed and can run whatever tool on Syngery. My leaks output currently shows the following:

   Process 5872: 701442 nodes malloced for 44682 KB Process 5872: 53 leaks for 3088 total leaked bytes.

   Note that it says 3,088 *bytes* are leaked. Which is 3 kilobytes or 0.002 megabytes. There are some known, tiny leaks in the system frameworks that account for this leakage, but it's so small anyway as to be insignificant.

   So what you're seeing isn't actually a "leak problem" at all but is quite normal. Try running leaks against some Apple applications, for example. These are some leaks figures for apps running on my machine right now:

   Safari: Process 22767: 1263 leaks for 43696 total leaked bytes.

   Finder: Process 234: 668 leaks for 40800 total leaked bytes.

   Mail: Process 23388: 92 leaks for 3232 total leaked bytes.

   Activity Monitor: Process 18184: 24 leaks for 10576 total leaked bytes.

   Terminal: Process 18267: 10 leaks for 336 total leaked bytes.

   And compare that with some non-Apple apps:

   TextMate: Process 18199: 480 leaks for 14656 total leaked bytes.

   SpamSieve: Process 23389: 8 leaks for 352 total leaked bytes.

   Net Monitor: Process 18186: 7 leaks for 176 total leaked bytes.

   I've got to run right now so can't write any more at this moment, but if you'd like more info on this topic let me know and I'll address it when I get back.

6. bugzilla user 472 2007-09-19T14:38:33Z

   Thanks for the additional information. I do realize that the leaks are expressed in bytes, and that the leaks utility does not uncover any significant leak. But the fact remains that Synergy uses a lot of memory (see attached screenshot). Or am I missing something?

   TIA

7. bugzilla user 472 2007-09-19T14:39:15Z

   Created an attachment (id=138) Memory used by Sygerny after 3 days

Add a comment

Comments are now closed for this issue.