Transmission

+1
*bump*

You can simply forget about that the Transmission devs will do anything about it. This problem has been in Transmission ever since version 1.7. It's completely unusable if it has to store received data over a network connection (e.g. what you call remote hard drives). There were threads about this i...

I might add: When I say it's killing all connections to local (LAN) ressources, you should know that these ressources are not connected to the same router, so it's not the router that's being overloaded or something like that. My devices are all connected to a professional, 24 port gigabit switch (H...

Hi, I've been using other torrent clients in the last couple of years because I was haunted by the infamous "leopard slow death" issue (see this thread: https://forum.transmissionbt.com/viewtopic.php?t=4564). I was never able to get this issue resolved, even after applying all suggested fi...

Old problem. VERY old problem. The devs are unable to fix this, most obviously. Transmission manages to completely kill Mac OS's network stack. All connections are interrupted.

This is a problem that's years old. I think it exists ever since v1.9x. Transmission *completely* kills the Mac OS network stack, all connections break. There is only one solution to this: Stop using Transmission. They weren't able to fix these bugs in ages so the software must be fundamentally flaw...

In my experience, Transmission is very intrusive to Mac OS X. It completely kills the whole network stack on a daily basis, forcing users to reboot or re-establish network connections. Since this issue has been present forever, I doubt it will ever be fixed.

@x190: you don't give up, do you? face it. these problems are real and they are in Transmission.

@gwallac: you're not alone.

Thanks. But again: I do not have any problems with other software that shuffles around huge amounts of tcp and udp connections. uTorrent never brings my whole system to a grinding halt like Transmission does. Same is true for Vuze. I read through that post you linked and I must say excuse me, but th...

I agree, but Devs shouldn't rule out their own software before they start to point at poor quality routers, logic boards and what not. I for myself can claim I know my stuff pretty well. I have professional IT experience (earning my money as an enterprise network architect) and I think I am pretty s...

I find it rather strange if users report problems to send them away "hey, research it yourself". If I were a developer (which I am not) and users of my software would report such problems, I would investigate them. It's like going to shop for christmas presents in one of these super large ...

I am already limiting speed to 8000 KB/sec. And why would I need to do that anyways? I download with uTorrent unlimited with 20 MB/sec and my system runs as smooth as baby ass. Don't let me stop you from using it! Counterpoint: Scroogle this! "system freeze +µTorrent" Ok, but what's your ...

Ehmtwo's concern is being dealt with here . funkahdafi likely needs to limit speeds and connections. I am already limiting speed to 8000 KB/sec. And why would I need to do that anyways? I download with uTorrent unlimited with 20 MB/sec and my system runs as smooth as baby ass. If Transmission has a...

I think I understand what you mean. You actually re-organized the file structure after the files were downloaded. That of course is a problem. Transmission won't find the files in that case. Your best bet is to keep using uTorrent to keep seeding those torrents. You could always use Transmission for...

I don't think the .torrent files actually store the information about where you saved the downloaded files to. That's something that should be in uTorrents config/database. Meaning, if you export the torrents, you can simply import them into Transmission. When you do that, Transmission will first ch...