Transmission causes leopard slow death

[Zorg]

Argh, there are definitely still issues with these new builds. I came back to my computer after a night of transferring and the screen saver was frozen, so I couldn't even get into see a beachball or have the option to quit. p.s. All my torrents are on an internal drive.

[loopkid]

I just tried the 6717 on Mac OS 10.5.4 with 28 torrents with 5 gb each and it caused a quick death to Transmission. After about 2 minutes the user interface is completely locked up. I triggered forcequit and it took several minutes for a complete shutdown, usually I even have to restart my system to restart Transmission.

Are these torrents stored on an internal hard drive, or on a usb drive, or a drive connected via the network, or some other situation?

The torrents are stored on an internal hard drive (SAMSUNG HM320JI).

[psykeeq]

Cmon guys...I thnik that transmission is one of the best/cleanest torrent client on Mac, so respect to every one who is working on this project, but this fuckin bug is frustrating and it makes me search for alternatives even if I dont want to (and there isnt any good alternative).
Its been 4 months since this thread was open (Thu Apr 10, 2008) and still no certian fix cmon... Can you tell me if you are working on this problem and when can we expect an update?

[mezz]

Cmon guys...I thnik that transmission is one of the best/cleanest torrent client on Mac, so respect to every one who is working on this project, but this fuckin bug is frustrating and it makes me search for alternatives even if I dont want to (and there isnt any good alternative).
Its been 4 months since this thread was open (Thu Apr 10, 2008) and still no certian fix cmon... Can you tell me if you are working on this problem and when can we expect an update?

Do you think it's simple to fix problems when most of us can't reproduce it? Come on, make yourself useful.

[psykeeq]

People already precisely described the problem...there are some crash log reports...
The only thing I can say that i have a Macbook (obviously that doesnt mater beacause people have the same problem on different machines types)...for me the bug started when i had about 5-10 torrents and there were couple of crashes back then, now I have about 20 of them and its impossible to run transmission for more than 2-3min. I know that is difficult to track down a bug but...its not that transmission uses an extra terestrial piece of code...its a fuckin torrent client...they all work in same/similar way.
I can post a crash log report if that helps...

[stace]

Add me to the list of people experiencing this problem.

I was happily chugging along with quite a high number of torrents for some time. After I installed the last security update from Apple, however, I can't run Transmission without locking the system, and producing these messages in my system.log.

Code: Select all

Sep  7 11:32:58 sasquatch kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:33:28: --- last message repeated 12 times ---
Sep  7 11:33:28 sasquatch kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:33:58: --- last message repeated 10 times ---
Sep  7 11:33:58 sasquatch kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:14: --- last message repeated 7 times ---
Sep  7 11:34:14 sasquatch kernel[0]: AppleYukon2: 00000000,00000010 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:15 sasquatch kernel[0]: AppleYukon2: 00000000,0000038e sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:15 sasquatch kernel[0]: AppleYukon2: 00000000,00000007 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:15 sasquatch kernel[0]: AppleYukon2: 00000000,00000006 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:16 sasquatch kernel[0]: AppleYukon2: 00000000,0000021d sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:16 sasquatch kernel[0]: AppleYukon2: 00000000,000001b8 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:17 sasquatch kernel[0]: AppleYukon2: 00000000,0000006c sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:17 sasquatch kernel[0]: AppleYukon2: 00000000,000003a3 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:19 sasquatch kernel[0]: AppleYukon2: 00000000,000003b0 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:19 sasquatch kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:19 sasquatch kernel[0]: AppleYukon2: 00000000,00000131 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:19 sasquatch kernel[0]: AppleYukon2: 00000000,000000d1 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:20 sasquatch kernel[0]: AppleYukon2: 00000000,0000022a sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:20 sasquatch kernel[0]: AppleYukon2: 00000000,000001e6 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:20 sasquatch kernel[0]: AppleYukon2: 00000000,0000021e sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:20 sasquatch kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:22 sasquatch kernel[0]: AppleYukon2: 00000000,00000013 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:22 sasquatch kernel[0]: AppleYukon2: 00000000,00000034 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:23 sasquatch kernel[0]: AppleYukon2: 00000000,000002d0 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:24 sasquatch kernel[0]: AppleYukon2: 00000000,000003b8 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket tried N times
Sep  7 11:34:25 sasquatch kernel[0]: AppleYukon2: 00000000,000003e8 sk98osx sky2 -  - sk98osx_sky2::replaceOrCopyPacket timedout

[essiw]

psykeeq fixing bugs/errors isn't as easy as you think it is. even one character could cause an error

[stace]

Given that pyskeeq says "its not that transmission uses an extra terestrial piece of code...its a fuckin torrent client...they all work in same/similar way.", I don't think he's going to get the nuances in code development. I'd save my breath.

[livings124]

stace: looks to be an issue with your hardware/drivers (as I expect this to be the case with many) http://forum.insanelymac.com/index.php? ... ntry853549

[kidmidnight]

stace: looks to be an issue with your hardware/drivers (as I expect this to be the case with many) http://forum.insanelymac.com/index.php? ... ntry853549

I dont think you get it. This ISNT a network problem. This ISNT the old router killing bug. Other computers can connect and surf fine. What this is, is an entire system crash. EVERYTHING beachballs once it happens. First you notice the internet is dead. Then you check your menu bar or dock and that beachballs. You cant force quit anything. Every other app beachballs.

I dont know what else you want us to say. This IS NOT an internet or hardware problem.

[livings124]

Did you even look at that link? It corresponds with the console output that was given. That's the only actual useful information I have been given - if you can provide some sort of useful information I can work with it. Have you tried lowering the peer connection limits to see if things improve? Or using the queue to limit the number of active torrents at one time?

If every app is beachballing, it clearly could be an issue with hardware/operating system.

[Zorg]

If every app is beachballing, it clearly could be an issue with hardware/operating system.

Unfortunately this problem only happened for me when I updated from 1.22 to 1.3+, and I didn't change any hardware nor update any part of OSX, so I think it more likely that Transmission is the source. My system only beachballs when Transmission is running, never at any other time. I've also run Techtool Pro to check for hardware errors, which came up clean and I optimised my disks too. Also, given that many people are experiencing the exact same problem as me, with different hardware configs points to Transmission too. Such a frustrating problem, because it freezes and doesn't generate any logs for us to give you. If it is the way Leopard deals with certain types of code, as the insanely mac thread suggests, then hopefully 10.5.5 clears this up for you.
I've lowered my global peer connection limits as you suggested - they were quite high at 2000! and so i lowered it to 100. I'll let you know how I go. Cheers

[livings124]

I've lowered my global peer connection limits as you suggested - they were quite high at 2000! and so i lowered it to 100. I'll let you know how I go. Cheers

Hence the warning about slowing down routers stated right below that field. Such a setting would surely have adverse effects on your computer usage.

[ozoner]

I love Transmission, and usually it works great, but for several days I have had exactly the problem described by kidmidnight: dead internet, menu bar beachballs, Transmission download speed drops to zero, everything beachballs. Basically all at the same time. Something is locking up the whole system. No way to force quit, so I have to turn machine off and restart.

It is definitely linked to Transmission, because it happens *if and only if* Transmission is running.

livings124: I tried lowering the number of peers who could connect, lowering the download speed to 50 (!), and only running one torrent at a time. None of it works. I don't know how to read the crash log in the console, but I didn't see anything obvious. I also noticed that Transmission was not actually downloading at the claimed speed. It would say "27 min, 58 sec remaining", and then take about 10 seconds to move to "27 min, 57 sec remaining", even though it was downloading at top speed! It doesn't normally do that. I have a wireless internet connection. The torrents are stored on the internal drive. I don't know what other information would be useful.

One more thing: The same thing happened last Winter, shortly after Apple released Leopard. There was a lot of speculation then that it was a problem with Apple, since people with different clients had similar problems. I checked Apple Discussions today, though, and found no complaints.

[ozoner]

Update: I downgraded to 1.22 as some earlier posts suggested, now it works fine. Thanks!