I have noticed now with a few releases that using Transmission with big files results in Transmission just hanging.. nothing but a beachball while it is creaing the files..
using iStat menus i can see (and hear) how busy my hard-drive is running while Transmission is simply fully locked.
once the files are created it continues to work as normal..
downloading a 50 GB torrent that contains 7 disk images resulted in a 25 minute long unstable system.. due to the extensive access to the hard-drive this has a very negative side effect to other programs that are running..
it doesn't happen with checking a file, only with creating large files..
beachball mayhem
-
xwaixwieda
- Posts: 1
- Joined: Fri Jul 10, 2009 12:30 pm
Re: beachball mayhem
For what's it's worth, I'm having the exact same problem. However, in my case it seems to occur with any file being created.
Re: beachball mayhem
I don't even think of that as a "problem" anymore; I've come to accept it as something I have to live with if I want to use Transmission.
The only thing you might try is to limit the torrent itself to one disk image at a time -- mapping out 50 GB of space at once is bound to take a lot of time. In the alternative, you could plan to start such a huge torrent just before you go to sleep - or just before you leave the house to do something.
The only thing you might try is to limit the torrent itself to one disk image at a time -- mapping out 50 GB of space at once is bound to take a lot of time. In the alternative, you could plan to start such a huge torrent just before you go to sleep - or just before you leave the house to do something.
Re: beachball mayhem
it actually does happen with every file that is created.. although it's not that noticable with the smaller files.. AFAIK it starts to really show from 4GB and up
coming with this problem is that it ONLY happens when the file is created.. and the file does not get created UNTIL you have received the first few bytes of it.. the problem with that is.. you just never know when it's gonna hit ya..
i am using a seperate drive just for Transmission.. this drive produces much more sound then 3 other drives combined and they are all the same.. but i have been toying with uTorrent.. nothing special there, it just goes up and down.. half the interface doesn't even work.. but it does not come with any beachball syndrome.. it's quiet (the drive is too) and fast and t works but I don't like it..
hopefully they do something about it
coming with this problem is that it ONLY happens when the file is created.. and the file does not get created UNTIL you have received the first few bytes of it.. the problem with that is.. you just never know when it's gonna hit ya..
i am using a seperate drive just for Transmission.. this drive produces much more sound then 3 other drives combined and they are all the same.. but i have been toying with uTorrent.. nothing special there, it just goes up and down.. half the interface doesn't even work.. but it does not come with any beachball syndrome.. it's quiet (the drive is too) and fast and t works but I don't like it..
hopefully they do something about it
Re: beachball mayhem
I've been having a similar problem, too.
Transmission often becomes irresponsive, parts of the UI get corrupted, and there is beach-balling all over the place. I also get the feeling that the entire system is being affected by this.
I was not able to find any cause for this behavior. I've played with all settings, disabled torrents, disabled/enabled speed limit, tried different speed limits, everything. I've also deleted lot's of files from the "resume" folder in transmissions app support folder.
You find four log files from samples taken with Activity monitor attached to this post. I hope they help fixing this issue.
Thx.
Regards
---
System: Macbook Pro 13"
OS: Mac OS X Leopard 10.5.7
Transmission version: Latest beta from the in-app updater
Transmission often becomes irresponsive, parts of the UI get corrupted, and there is beach-balling all over the place. I also get the feeling that the entire system is being affected by this.
I was not able to find any cause for this behavior. I've played with all settings, disabled torrents, disabled/enabled speed limit, tried different speed limits, everything. I've also deleted lot's of files from the "resume" folder in transmissions app support folder.
You find four log files from samples taken with Activity monitor attached to this post. I hope they help fixing this issue.
Thx.
Regards
---
System: Macbook Pro 13"
OS: Mac OS X Leopard 10.5.7
Transmission version: Latest beta from the in-app updater