1,3x: Session Transfer Vs Actual Download (Fixed in 1.40)

[joydivision]

So, seeing that this Bug has been fixed in latest code, how can I update?
It's that I'm using Linux, and normal build version 1.34 does show that critical bug here: only about 1/5 is downloaded actually to the file, all the rest of downloaded data is wasted...
Now I see you fixed it, but nightly builds appear to be only for MacOS?!
Anyway to get the actual source code to build it on my machine?
Or, any plans of releasing 1.35 with this bug fixed, soon?

P.s: funny thing is that on my other machine, version 1.32 is not showing the bug...

[Jordan]

The reason that it differs between 1.32 and 1.34 is not because of the version number... it's because the problem only manifests itself in some swarms, during connections to some peers, but not others. That's one reason why it was hard to get nailed down.

I had hoped to go straight to 1.40 after 1.34, but it might be good to put this in the bugfix branch too (i.e., a 1.35) since maintenance releases are going to be more palatable to Linux distros that ship with Transmission.

[Jordan]

I've got a new & improved fix in r6954 now. There wasn't really anything wrong with the previous fix, but I figured out a way to reduce the overhead a little more, faster, and using less memory. Win-win-win scenarios like that don't happen every day, so I'm still looking for the downside... I'd appreciate nightly users to give it a spin and see how it goes.

Here's a test torrent I downloaded from legaltorrents.com. There was only about 1.5 MiB overhead for a 186 MiB torrent. YMMV depending on the number of peers in the swarm and the size of the torrent, but the percentages for stuff downloaded with the new code should still be pretty good.

[McFly3]

I have been using T1.34+ (6960). I observe that this is much better. I still notice that at times, the total upload / download speed is more than the one displayed for the individual downloads. The ETA is much better with this build then the previous T1.34+ nightly builds.

[joydivision]

I've got a new & improved fix in r6954 now. There wasn't really anything wrong with the previous fix, but I figured out a way to reduce the overhead a little more, faster, and using less memory. Win-win-win scenarios like that don't happen every day, so I'm still looking for the downside... I'd appreciate nightly users to give it a spin and see how it goes.

Here's a test torrent I downloaded from legaltorrents.com. There was only about 1.5 MiB overhead for a 186 MiB torrent. YMMV depending on the number of peers in the swarm and the size of the torrent, but the percentages for stuff downloaded with the new code should still be pretty good.

Great.

I'd happily test, but I don't know how to get the r6954... would please someone explain me, how I can compile or where I can get, that nightly build version for Linux?
All I can find on your site is nightly builds for Mac, and the official version (1.34), which I have and which still has the bug...

[livings124]

joydivision
http://www.transmissionbt.com/development.php has directions for getting the code.

[skenliv]

I guess it´s in the nightly build as well?

This must have been quite a persistent bug, i have had problems with speeds last time i used transmission to.

[trinket]

I have had this very same problem with Transmission since it's first release. At the time I remember raising the issue, and was told by forum admins that I was creating unwanted 'hype' around a 'non existent' problem. It is sad that it still has not been resolved.

I stopped using transmission altogether because of this issue in favour of BitRocket, but since BitRocket hasn't been updated and is super unstable, thought I would give Transmission another try. I have a 50gb download limit, and had 20GB + left in my quota, but after using Transmission ONCE for downloading 3 files (each was 250-350mb in size), I got a warning from my ISP that I was 1GB off my quota.

It is a problem that should be addressed, and I am a little peeved that after all this time, it still hasn't been fixed, and even more people are experiencing this problem.

Many people are charged for excess downloads, and I think it is unfair that users of Transmission have to pay these excess fees because of a software glitch. It isn't as simple as end user misuse.

[Toby]

trinket, what version of Transmission do you refer to when you say 'first release'? This problem has only been around since version 1.30.

What version of Transmission were you using when you downloaded these files? If you have read the posts above your own, you will know that a majority of users are saying that the problem has been fixed in the latest nightly release (available here for Mac and here for Linux.) If you experienced this bug, it would be useful for you to do some reading about the current efforts to fix it beforehand (as it seems you have not done so,) rather than just complaining about the inconvenience it is causing you. It is not very polite to say that you're "peeved" that problem "still hasn't been fixed" when the developers are working very hard (voluntarily) to provide a solution.

[Jordan]

I have had this very same problem with Transmission since it's first release. At the time I remember raising the issue, and was told by forum admins that I was creating unwanted 'hype' around a 'non existent' problem. It is sad that it still has not been resolved.

URL?

[trinket]

I am not disputing the fact that you're working hard - but when I first raised this issue (and this was about 2 years ago!!), I was shot down and told there was no such problem, and I was surprised that after downloading transmission again that the issue was still occurring for me. I am now too freaked to use the newly released builds because the cost for me is too great if it does end up happening again. That was the essence of my message, which I obviously didn't communicate well.

And for the record - I DID read the thread before posting, but not everyone using the newer version quoted (which is now obsolete) mentioned that it had been a 100% fix, thus - it is still an issue.

[Jordan]

when I first raised this issue (and this was about 2 years ago!!), I was shot down and told there was no such problem

None of the current developers were here two years ago. I'm sorry if you were treated harshly at the time but it's got no bearing to what's going on today.

I am now too freaked to use the newly released builds because the cost for me is too great if it does end up happening again.

Then I'm not sure what you hope to contribute to this thread other than your exasperation, which is understandable but not productive. I'd rather hear from other users who are willing to test the nightlies and give feedback on them.

[skenliv]

This is just rediculous, transmission is downloading in 5-7kb/s and utorrent in the virtual machine (BEHIND FIREWALL) downloads @ 6-700kb/s.... In the newest 1.4.0 version!

[alison87]

I think this is a different problem. 1.40 hands down fixes the issue being discussed in this thread, better even than it was in 1.22 i think! The slow download thing appears to be something else. And i know i would much rather have a slow download that actually downloads what it says it does than a fast one that blows my bandwidth cap.

[skenliv]

Agreed, this thread is relative to 1.4.0 now. -> http://forum.transmissionbt.com/viewtop ... f=2&t=6388