Memory Leak in Transmission 2.33 OSX Lion?

[moilejter]

A couple of times recently, I've come back to my computer to find it nearly unresponsive. Looking around, I noticed that Transmissions memory usage had ballooned to >6GB (I have an 8GB Mac mini). The first time this happened, I was running 2.33; the second time I was running the most recent build (12632). I restarted the app both times, and it seemed to behave on startup.

I'm not sure what kind of information I can collect to submit here, next time it happens - but if you have any suggestions, I can follow them and submit any data collected, then ...

[livings124]

Can you provide any more specific information. Does memory usage increase for any specific actions? Can you provide a Shark profile? https://trac.transmissionbt.com/wiki/Shark

[jordan]

moilejter: ping

[livings124]

Please reopen with more information.

[ajuhasz]

I'm also having this problem. It seems to occur when a torrent download is completed and the file needs to be moved from the 'downloading' directory to the 'downloaded' directory. It also seems to only happen if multiple torrents are being downloaded at the same time. The file itself it copied into the 'downloaded' directory, but when I reopen Transmission the percent downloaded is at <100.

I tried opening shark in lion but it just closes with no error, I did use activity monitor to take a 'sample', but I couldn't upload it (file size too big).

[livings124]

Going slow when moving data is not the same as a memory leak. Does the memory return when the move finishes? Can you try to post relevant bits from the sample?

[ajuhasz]

The copy happens at full speed.

More details: the memory leak (slowly growing memory footprint of transmission) happens on the second copy of the application session.

Sorry to be thick, what would be the relevant section?

[livings124]

Can you try to replicate this with a nightly build from ​https://build.transmissionbt.com/job/trunk-mac/?

[ajuhasz]

Using build 12696, I can't replicate the huge memory increase.

I did notice the memory did increase ~5MB after three downloads, though it has remained stable after that. The gain was after the downloads were complete from 69MB to 74MB.

Thanks for the help!

[livings124]

Sounds good. Closing, but feel free to reopen if there are more issues with this.

[moilejter]

Sampling of app taken by Activity Monitor.

[moilejter]

It had not repeated for me, until just now - still using v12632. I took a sampling using MacOSX's Activity Monitor when its memory use had reached about 2.4GB. I will try downloading a newer nightly... (I forgot about using Shark... I will try that, next time.)

[livings124]

Hey moilejter, a log from a current nightly would be much more useful. There's not much I can do with the sample you gave me.

[moilejter]

Sorry :-( - I had not kept up with your nightlies... I have updated now, and will keep updating daily, in case it happens again. An item that might be relevant: I am on a DSL connection, and sometimes the connection drops momentarily then reconnects. When that happens, however, existing socket connections seem to just hang, rather than either closing or resuming transmission. I don't know whether this app might be sensitive to that...

Is the sampling from Activity Monitor enough, if this happens again - or should I look into using Shark, next time?

Thank you!

Moises

[livings124]

The way you're doing it now is good. A new nightly is needed because we changed some settings in the nightly build set up to give us better debug info.

[livings124]

I'm going to close this for now - there's nothing I can do with the info I have. Please reopen if you can repeat with a current nightly build.