Transmission causes leopard slow death

[Feek]

I had this problem for the first time a couple of weeks ago and ended up removing Transmission completely and switching to uTorrent.

Today I decided to see if it was a known issue and found this thread - I reinstalled Transmission and added the sysctl.conf file as described but within 15 minutes of it running, the slow death started. I had enabled the speed control and then just hidden transmission and not touched it any further.

*sad*

[mofle]

I have had this Slow Death problem after I upgraded from 1.41. After a lot of trouble I went back to 1.41 again. Today I thought I should try 1.61 with a hope that the bug was fixed. I had of course completely removed all preferences and files belonging to the 1.41 version before I installed the 1.61.

I just tried to download one torrent without Speed Limit enabled, and to my "surprise" after just a couple of minutes Transmission froze, and then shortly after my Mac froze.

Here is the Console output, hope it helps.
(I don't have time to test the nightly version, I have tried that a lot of times before without any luck. Neither have I tried the syctl.conf fix).

I seems like there is some conflict with VMware Fusion (vmnet).
http://communities.vmware.com/thread/161605


My config: MacBook Pro 10.5.7

Code: Select all

26.05.09 01.10.35 hdiejectd[10206] running
26.05.09 01.10.40 [0x0-0x48f48f].org.m0k.transmission[10198] "disk1" unmounted. 
26.05.09 01.10.40 [0x0-0x48f48f].org.m0k.transmission[10198] "disk1" ejected. 
26.05.09 01.13.52 kernel AirPort: Link Down on en1 
26.05.09 01.13.52 kernel vmnet: bridge-en1: interface en is going DOWN 
26.05.09 01.13.58 kernel vmnet: VMNetDisconnect called for port 0xea73700 
26.05.09 01.13.58 kernel vmnet: bridge-en1: filter detached 
26.05.09 01.13.58 kernel vmnet: bridge-en1: down 
26.05.09 01.13.58 kernel vmnet: bridge-en1: detached 
26.05.09 01.13.58 kernel vmnet: Freeing hub at 0x973c000. 
26.05.09 01.14.01 krb5kdc[68] Interrupted system call - while selecting for network input(1) 
26.05.09 01.14.01 krb5kdc[68] Interrupted system call - signal_requests_network recieved 
26.05.09 01.14.02 com.apple.launchd[1] (org.samba.smbd[6382]) Stray process with PGID equal to this dead job: PID 6384 PPID 1 smbd 
26.05.09 01.14.04 krb5kdc[68] setsockopt(IPV6_V6ONLY,1) worked 
26.05.09 01.14.06 kernel AirPort: Link Up on en1 
26.05.09 01.14.06 kernel vmnet: VNetUserIf_Create: created userIf at 0x9075200. 
26.05.09 01.14.06 kernel vmnet: VMNetConnect: returning port 0x9075200 
26.05.09 01.14.06 kernel vmnet: Hub 0 does not exist, allocating memory. 
26.05.09 01.14.06 kernel vmnet: Allocated hub 0x8a36000 for hubNum 0. 
26.05.09 01.14.06 kernel vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:f4:39:14 
26.05.09 01.14.06 kernel vmnet: Hub 0 
26.05.09 01.14.06 kernel vmnet:  Port 0 
26.05.09 01.14.06 kernel vmnet: bridge-en1: got dev 0x78b9004 
26.05.09 01.14.06 kernel vmnet: bridge-en1: wireless interface detected. 
26.05.09 01.14.06 kernel vmnet: bridge-en1: up 
26.05.09 01.14.06 kernel vmnet: bridge-en1: attached 
26.05.09 01.14.06 kernel vmnet: VNetUserIfFree: freeing userIf at 0x9075200. 
26.05.09 01.14.09 krb5kdc[68] Interrupted system call - while selecting for network input(1) 
26.05.09 01.14.09 krb5kdc[68] Interrupted system call - signal_requests_network recieved 
26.05.09 01.14.12 krb5kdc[68] setsockopt(IPV6_V6ONLY,1) worked 
26.05.09 01.14.12 com.apple.launchd[1] (org.samba.nmbd) Throttling respawn: Will start in 2 seconds 

[kidmidnight]

yo parodyr, your fix is working perfectly 2 weeks in now!

[Jordan]

I'm wondering if any of the really-early-adopters of 10.6 have anything to say about whether or not this issue exists on Snow Leopard...

[Alesc]

Hello there !
Same issue here: Transmission is killing my Leopard, with or without "Speed Limit" enabled.
So I've tried some other clients, but I miss Transmission... I hope a day this issue will be fixed... But too much hard reboot: I'm not usint it anymore... And I'm waiting for the bug fix...

[tolen]

To be brief, Transmission has ruthlessly takes over my Mac Pro, when running. My UL limit has been set to 35K for a couple months now, as it has been since settling of RR's practical limits. Since installing 1.70 running ANY other communications apps is problematic. Time-outs and 404 errors are common in web browsers. Usenet clients often fail to even verify passwords, and even Mail has failed upon occasion.
As a noob, I figured at first that the problems were caused by my trying to UL or DL too much. Pausing or eliminating all but 5 seeds, and confining Transmission to just 2 downloads has not helped.

Other apps are affected as well. My .mov files stutter and hang, for example.

This is the 2nd time snooping the forums for a resolution to this matter. At first just seeking info on down- or retro-grading without losing active seeds & such, having found nothing in "Help." Discovering that many here have been having similar problems since about v1.6, I quit for the day, not quite sure with which version to replace this 1.7.1.

Coming back today, I found this thread, and felt compelled to chime in. This is the only BT client I've ever used. I've been most grateful for its miraculous ease of use and efficiency. Now my "reply" having hung, I'm ending this in "Preview", signing off and sending, before something worse happens.

[livings124]

To be brief, Transmission has ruthlessly takes over my Mac Pro, when running. My UL limit has been set to 35K for a couple months now, as it has been since settling of RR's practical limits. Since installing 1.70 running ANY other communications apps is problematic. Time-outs and 404 errors are common in web browsers. Usenet clients often fail to even verify passwords, and even Mail has failed upon occasion.
As a noob, I figured at first that the problems were caused by my trying to UL or DL too much. Pausing or eliminating all but 5 seeds, and confining Transmission to just 2 downloads has not helped.

Other apps are affected as well. My .mov files stutter and hang, for example.

This is the 2nd time snooping the forums for a resolution to this matter. At first just seeking info on down- or retro-grading without losing active seeds & such, having found nothing in "Help." Discovering that many here have been having similar problems since about v1.6, I quit for the day, not quite sure with which version to replace this 1.7.1.

Coming back today, I found this thread, and felt compelled to chime in. This is the only BT client I've ever used. I've been most grateful for its miraculous ease of use and efficiency. Now my "reply" having hung, I'm ending this in "Preview", signing off and sending, before something worse happens.

Have you even read this thread?

[guilherme]

I'm wondering if any of the really-early-adopters of 10.6 have anything to say about whether or not this issue exists on Snow Leopard...

Transmission still slowly dies, but I'm able to force-quit it without affecting the rest of the system. Well, that's at least an improvement, right?

[tolen]

to: livings124

What a stupid question. Of course I had. I can understand your being in a bad mood, what with your Transmission problems, but I'd rather you not take out your frustrations on me.

If you think me impertinent, please explain.

In fact, I had Transmission running in the background as I was writing. Upon trying to edit and condense what I'd written, the blinking vertical line indicating the text insertion point disappeared, so unable to continue, I hit the Submit button. I then added a line in "Preview" mode hit the Submit button immediately, lest all I'd written were lost.

The problems apparently caused by this 1.70-1.71 build are so numerous and detrimental to my workflow, I shortly thereafter posted regarding downgrading from 1.71 to 1.6, without losing ULs and DLs in progress.

…may you have a better day

[livings124]

So the solutions proposed in this thread did not work? Please elaborate on what you did.

[Feek]

So the solutions proposed in this thread did not work? Please elaborate on what you did.

I did exactly as had been suggested in this thread and I still have the slow death problem, see my post just a bit above here:

I had this problem for the first time a couple of weeks ago and ended up removing Transmission completely and switching to uTorrent.

Today I decided to see if it was a known issue and found this thread - I reinstalled Transmission and added the sysctl.conf file as described but within 15 minutes of it running, the slow death started. I had enabled the speed control and then just hidden transmission and not touched it any further.

*sad*

[IkMarvel]

I am so glad that I came across this forum. I have been having trouble with Transmission bringing down my machine for a few months. EVERYTIME. I just downloaded Utorrent for Mac and it's does the same thing, unfortunately. I kept thinking it was things I had installed conflicting with everything else. Sure enough I would start Transmission and after a short while it would kill my machine.

I just downloaded an older version " Transmission 1.05" and WOW. I'M BACK! No problems what so ever, and now I don't feel like I have to reformat my computer - which I came very close to doing.

Yippee!

[Cordieri]

To be brief, Transmission has ruthlessly takes over my Mac Pro, when running. My UL limit has been set to 35K for a couple months now, as it has been since settling of RR's practical limits. Since installing 1.70 running ANY other communications apps is problematic. Time-outs and 404 errors are common in web browsers. Usenet clients often fail to even verify passwords, and even Mail has failed upon occasion.
As a noob, I figured at first that the problems were caused by my trying to UL or DL too much. Pausing or eliminating all but 5 seeds, and confining Transmission to just 2 downloads has not helped.

Other apps are affected as well. My .mov files stutter and hang, for example.

This is the 2nd time snooping the forums for a resolution to this matter. At first just seeking info on down- or retro-grading without losing active seeds & such, having found nothing in "Help." Discovering that many here have been having similar problems since about v1.6, I quit for the day, not quite sure with which version to replace this 1.7.1.

Coming back today, I found this thread, and felt compelled to chime in. This is the only BT client I've ever used. I've been most grateful for its miraculous ease of use and efficiency. Now my "reply" having hung, I'm ending this in "Preview", signing off and sending, before something worse happens.

Have you even read this thread?

After 390 post and 27 pages, if you dev guys haven't been able to fix the app, what about a bit of humility?
I too have left Transmission for same reasons for uTorrent and was back for an eventual fix in a new version; tested last stable and still same stuff .
Whaterver solution you may propose here is in any way a good one; the app by itself should not provoque slowdown and kill traffic.
So no, perso I won't read all this thread to find out some esoteric command line solution or other, I will just wait for you dev guys to do your homework and fix the bugs that have been reported since a long time now.

[livings124]

Cordieri: If you can't read a few posts back, then that's not my problem.

[essiw]

lol, they do this for free you know. and if it is 27 pages long doesn't that mean that this is a huge problem and they are already trying the best they can? you Cordieri should show some respect to them, instead of saying that they could have fixed it already, if it is that simple why don't you fix it yourself? it is open source.