Transmission 1.80 beta 5

[Longinus00]

Is there a precompiled or rpm version of this latest beta?

Transmission frontpage?

Only mac binaries are available on the front page. The give away that they want a linux binary is from the rpm request.

[nilshaus]

I don't know if the devs actually care about this, but I installed beta b/c I saw something about the better management of large number of torrents, but scrolling still pegs one of my cores, and transmission takes up about 20% of my cpu with 0 download/upload activity.

[Yada]

Good! Now do it again with r9934.

Running r9934, will report back.

It has run fine until now, so unless you hear something from me you can assume it's been fixed

[essiw]

I've got a question not specific on the last beta but more on all beta's. Why am I not able to resize the adding torrent window (I am only able to make it a bit smaller but not bigger) I really dislike that because most of the names of the files I download are big and the first part is the same, so I have to check what I download at the inspector menu after adding it, And I have to scroll to see what files are beneath the others which is not practical. I am sorry if this has been questioned before. thanks in advance for your answer

[shawnbon206]

http://forum.transmissionbt.com/viewtop ... f=4&t=9315

^ Crash reported

[Jordan]

http://forum.transmissionbt.com/viewtop ... f=4&t=9315

^ Crash reported

This appears to be the same bug Yada reported a few posts up and appears to be fixed in the nightlies. Could you try upgrading to a nightly and see if that makes the crash go away for you?

[livings124]

The nightly builds have a change to the backend that should result in lower cpu usage. Can we have feedback? http://transmission.xpjets.com/

[slyborg]

Related note...I may just not have noticed this before, but I see Transmission burst up to 100% CPU on one core for 30-40 secs every 4-5 minutes. This is with 3 torrents each single tracker and ~700 known peers total. I think this is new behavior, actually, because it's kind of annoying when running other CPU-intensive apps and I think I would have noticed it before.

I'm currently seeding the 3 torrents, so no d/l at all.

Mac Mini 2 GHz, 4GB, 10.6.2, b5.

[livings124]

slyborg: this is with the latest nightly, as I just stated in the post above?

[slyborg]

slyborg: this is with the latest nightly, as I just stated in the post above?

No, beta 5, as I indicated. Let me try the nightly....

Edit: Hm, looks like you found that nested loop Much better, no unusual CPU usage with same torrents on b9945. Thanks....

[livings124]

Not a nested loop.

[slyborg]

Spoke too soon on b9945 ;_; Looks like it's still doing it, I was confused because istat was reporting the process as 'launchd', before it was showing up as Transmission itself. Running top shows it as Transmission. What's odd is that it did seem ok for an hour or so. I see it spiking to 100% once for each torrent for a length of time proportional to the number of peers on the tracker, every couple of minutes looks like. The high number would be ~1500 peers on the tracker, and for this one it runs at 100% for about a minute.

Don't think I'm doing anything special, should be reproducible on any torrent with a lot of peers....

[Nemo]

Is there a precompiled or rpm version of this latest beta?

Since a few weeks there are 1.80beta-builds in Fedora's Rawhide. (Read the following blog-post of Rahul Sundaram - "Transmission changes in Rawhide" for more info.)

If you're running Fedora 12, you can update using

Code: Select all

yum update --enablerepo=rawhide transmission

Or pull a transmission-build direct from Koji (The Fedora build-system).

[livings124]

Spoke too soon on b9945

I should of said the nightly build that should have fixed the cpu issue is at a minimum 9947.

[slyborg]

Spoke too soon on b9945

I should of said the nightly build that should have fixed the cpu issue is at a minimum 9947.

Ok. Latest available on xpjets link above is 9945 (?) Via the "latest" link. I don't want to build the thing myself...