Transmission causes leopard slow death

[comctrl6]

I updated from 1.61 to 1.71 and started having the issue. Transmission would work fine for a few minutes -- usually about 20 minutes -- then it would lock up and slowly take the entire system down with it. This happened multiple times when I was using 1.71.

I downgraded to 1.61 and everything has been working flawlessly ever since the downgrade. There was no OS change in the time period since I updated to 1.71 and downgraded to 1.61, so this could not possibly be an OS issue.

Now there is an update available and I'm afraid of updating since I don't want my machine to turn into a brick. Can someone confirm/deny 1.72 doesn't have this issue?

FYI, I'm on a Mac Mini running Leopard with the latest updates (10.5.7). My files are downloaded onto an external USB hard drive.

[timta2]

Since upgrading to 10.5.7 and using the latest versions (1.7x, now 1.72) I have not experienced any more "Leopard Slow Death" issues. Its been a month.

I agree that it seems like an OS issue.

[VoRa]

I'm on OS X 10.5.7.

One week ago I used the latest Transmission version (idk if it was 1.71 or 1.72, however it was the latest at that time), and then my system was killed by Transmission all the time.

Now a week ago or so I downgraded to 1.52, everything is smooth, no problems. I guess 1.61 will work fine as well, I dont see any reason to upgrade though - things work fine as it is. All I know is if I use the latest version my Mac dies.

[mgnewman]

Interesting. I've been using the latest version of Transmission for nearly a year now and have never noticed this problem, until today. I've gone back and searched the system.log for the past week and the first instance of:

sockwall_cntl_releasecachedpath ctl_enqueuedata rts err 55

was today about 4 PM, just after I downloaded the latest (4.0.1) version of Safari. Every time I got the "slow death" crash that error appeared in the system.log.

I've downgraded to 1.52 and all seems well.

[redstar]

I seem to suffer from this as well.

I am running Transmission 1.72 and OSx 10.6.5.

When I limit bandwidth using either the Global Bandwidth or Speed Limit option, after five minutes or so my system hangs - I can't force quit anything and have to power the machine off manually. Disk activity appears to be minimal - I can't check using the activity monitor, but there is no obvious swapping or disk activity occurring.

If I am connected to the internet via my Airport Express, the Airport also stops allowing any client connected to it to get onto the web.

If I am connected directly to my building's network via ethernet, clients connected via the Airport Express can continue to work.

Running Transmission with lots of downloads and uploads going but no limits works fine - I just have to pause and restart it if I need to use my laptop to do something else.

I hadn't used Transmission for a while and had never used any bandwidth limits previously when I started using it again, so I can't refer back to previous experience.

Other BitTorrent clients do not have this issue.

[olk]

I have the same problem on slow death.
First it kills network (Net Monitor shows 0 in 0 out) and then everything else hangs. I have to force reboot my iMac.
Running 1.72 and OS X 10.5.7

It is obviously Transmission issue, as it only appears with using this app.
Has anybody got some solution?

[essiw]

It is obviously Transmission issue, as it only appears with using this app.
Has anybody got some solution?

Maybe reading the topic would be a good solution?

[olk]

It is obviously Transmission issue, as it only appears with using this app.
Has anybody got some solution?

Maybe reading the topic would be a good solution?

I have read this topic through. The suggestion of changing recv and sendspace is not working for me.
There is no other apps, that have this problem

The last working version of Transmission is 1.5x I guess, there was no problem then.
So it is not an OS issue.. So any solution?

[livings124]

It is an OS issue. We have shown this.

[cheule]

If there is a viable workaround why not post that?

Back on page 22 through 25 of this thread (info that I might add it almost 2 months old) cites it is a bug introduced with the new networking code in Leopard. Discussion also points to two things;

1) use of speed limit mode seems to be the major culprit. Leaving it off seems to solve the networking issue with Leopard.

2) adding a conf file into your /etc folder to disable some of the new auto network sizing in Leopard fixes the issue, and then you can use speed limit all you like.

See this post for instructions on how to implement this "viable workaround." And note I too had all the issues people have been complaining about in this thread, I made that sysctl.conf file, and everything works now. I'm only surprised that more people can't seem to find the info that they seek, in the exact thread they post looking for help.

[ganjaia]

I have been having this problem for quite some time. In my case I'm fairly certain it's a bug in Apple's Yukon2 network adapter driver, it just so happens to be triggered by Transmission. I have an Intel Mac Mini connected to a gigabit LAN via ethernet. I download files to SMB shares on a Synology NAS server. I think this combination triggers the bug in the network adapter drivers and I the ethernet connection dies. The only way to get it working again is to restart the machine.

Checking my system logs I see the kernel AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times errors. As a suggestion, everybody should check Console to see what the actual errors are when the beachball shows up. That would really help determine if it's OS or app specific in your particular case.

I'm usually alright if I don't have too many torrents running at the same time. But that kind of defeats the purpose of sharing, especially when ratios are involved. ... I just hope Apple fixes this in Snow Leopard.

[kidmidnight]

This forum thread has endured a slow death. People are unwilling to acknowledge that this is an OS issue.

which is why every other osx bittorrent client causes this issue right

[cheule]

If you've read this thread, there are many many reports that this networking bug occurs with utorrent and Azeureus as well. Not everyone reports this, but there are many in this thread alone.

[kidmidnight]

if you read this thread you would know it was me determined what caused this. and no, no other clients dont cause this.

[SG-]

i'll have to do more testing, but so far snow isn't doing this for me on my machine anymore.