Transmission

Seeding works fine in r10980, thanks.

r10954 built as release exhibits the bug while built as debug it doesn't, but hey...

r10977 works. I went back to an earlier revision and tested, and the likely reason you couldn't reproduce this is because you're using debug builds while I (like most users I would assume) am using release builds. We've had this same situation before, so you may want to keep this in mind when you ha...

I can confirm that this broke somewhere between revisions 10930 and 10954. Would it be possible to track down which revision it was that broke it? I'm not seeing this behavior... It was broken before 10948. The Mac version didn't build between 10931 and 10947, so testing those changes will require ...

I can confirm that this broke somewhere between revisions 10930 and 10954.

livings124 wrote:Is there a procedure needed besides just resizing the window?

No, but you do need a torrent with several files.

Does it happen in the latest nightly?

Yes.

If you have a torrent with many files, the completion rates will be displayed only for the first ten or so files. Interestingly the number of rates shown depends on the width of the inspector window, which suggests the system calculates the cumulative length of all the completion rate strings and us...

Tested with r9950, no change. I don't think the beachballing is a problem in libevent, but rather an architectural one in that the main thread is allowed to block on network access which does not have a guaranteed response time. Call graph: 5822 Thread_833952 DispatchQueue_1: com.apple.main-thread (...

When opening some torrents, Transmission starts to beachball frequently. Process samples show this is because the main thread is blocking on some torrent's lock. The torrents this happens with tend to be of the "massive list of dubious trackers" kind, so maybe some operation which holds th...

It seems that the duplicate trackers were a red herring and that the program will always delete the tracker preceding the selected one (and crash doing so). The tracker deletion code certainly looks convoluted enough for any number of bugs to be hiding in it.

Different tiers. (I wish I could pass on this torrent, as it's a beauty. It has 158 tiers, and that's after I manually removed a bunch of trackers.)

Suppose a torrent's tracker list looks like so: 1: a 2: b 3: c 4: c 5: d If you select tracker 3 and click on the remove button, the result is 1: a 2: c 3: c 4: d If you would have selected tracker 4 and removed it instead, the result is the expected 1: a 2: b 3: c 4: d In addition I've had Transmis...

This is probably the same bug as I described here. Try selecting all duplicated trackers and remove them first, then trim the non-working ones.

I don’t think it’s a good idea. What if Finder says you have enough free space for the whole torrent, but Transmission refuses to download another bit of it? I think it’s confusing if you don’t know what happened to the file size calculation. Congratulations, you've just described the current situa...

Apple in their infinite wisdom decided to start calculating file sizes in multiples of 1000 instead of 1024 as nature intended. One consequence is that the file sizes are not the same in Transmission's UI as in Finder anymore. It looks like this would be a minor change, just add a divider variable t...