[unofficial]qBittorrent git master builds: 3.2.0alpha_20150308_19b9a84

[tekko]

[quote="sledgehammer_999"]
qbittorrent_3.2.0alpha_20150203_6209d88_libtorrent0.16_setup.exe
[/quote]

Works well for me, Thanks. Probably had to do with huge sized torrents and torrents with many files.

When I upgraded from stable to previous alphas, the columns changed. I had to choose the columns again. This one stays the same for the columns. Libtorrent's version affects the columns? This one is not a problem, just testing throught things and taking notes of the differences.

[Nemo]

Thanks sledge, installed and tested right away.

Libtorrent 16.19 seems less sensitive with uTP compared to 1.0.3 with my tests but I came to the conclusion that this isn't a huge problem for me. Maybe Chrome is causing this by asking too much bandwith and so is uTP being triggered, might test Firefox to see how that works. Or the uTP in libtorrent 1.0.3 needs some fine tuning perhaps. Overall im okay with libtorrent 1.0.3, everything else works perfect. I installed the other alpha again with 1.0.3 and will be using it as my main. My doubts/questions are over by this

@tekko: Did you tried a clean install also just in case? Just a guess though .

[tekko]

[quote="Nemo"]
@tekko: Did you tried a clean install also just in case? Just a guess though .
[/quote]

With the alpha from December, I did a clean install once. The problems came soon after I force rechecked the torrents.

A force recheck of the whole list takes me a whole day and modifying the trackers and custom paths is time consuming.

I understand that upgrading/downgrading might cause compatibility problems if I don't do a clean install. But spending time to set qbt up all over again and see the problem anyway, just kills me.

[tekko]

https://github.com/qbittorrent/qBittorrent/issues/2365
https://github.com/qbittorrent/qBittorrent/issues/2366

All gone in "qbittorrent_3.2.0alpha_20150203_6209d88_libtorrent0.16_setup.exe"

[Nemo]

So using libtorrent 0.16 instead 1.0.3 fixes most of the issues right away?

Hmm.. Both run good here though without any weird cpu usages or situations, what I see is that when im maxing my speed the cpu usage is around 5-15%, thats normal I guess (with 1.0.3 libtorrent alpha build)?

Also what makes me wonder is; does newer libtorrent handle certain things different than 16.19?

Would be nice if we could get some more feedback from the alpha users about this.

[ciaobaby]

My dev machine, Qbt 3.2, lt 1.0.1, Linux Mint 16, Two Xeon Core 2 Duo, 16G ECC RAM, 30 jobs running, 1 download, rest seeding.

qBT is using ~125 M RAM, CPU avg 2%

Calibre is using more resources converting 10 books to AZW3

[tekko]

[quote="Nemo"]
So using libtorrent 0.16 instead 1.0.3 fixes most of the issues right away?
[/quote]

1.0.3 doesn't do well with big torrents I guess.

I would like to see more alpha testers giving feedback also.

[tekko]

I've encountered a problem with the new "missing files" status. I used "set location" to change the locations of some torrents at some point. Something happened in between, but I forgot what. One of the torrent now says "missing files". I force rechecked and it gets to 100%. It CAN find the file (tested with "preview" and in torrent content), but the status just won't go away when paused. I resumed the torrent and the status says "seeding". It says "missing files" again when paused...

UPDATE: back to normal after restarting qbt...

[PoMcku]

This is http://builds.shiki.hu/temp/qbittorrent ... _setup.exe connecting to peers very slow and connecting with little amount of peers, as compared with http://builds.shiki.hu/qbittorrent_3.2. ... _setup.exe,
But

https://github.com/qbittorrent/qBittorrent/issues/2365
https://github.com/qbittorrent/qBittorrent/issues/2366

All gone in "qbittorrent_3.2.0alpha_20150203_6209d88_libtorrent0.16_setup.exe"

[Nemo]

Im very happy with the latest alpha since using it after it got released. I was a little bit sceptic about the uTp behaviour but things are working alot better now so im taking back what I had said. Can't wait for v3.2.0 stable !

Don't let the name ''alpha'' fool you, this is just as stable as official releases.

[sledgehammer_999]

Here is a build of qBittorrent 3.2.0alpha sha1 19b9a84 from git master with:
boost 1.55
libtorrent 1.0.3svn+r10821
qt: 4.8.6

Built using msvc2013

Git changelog from last alpha: https://github.com/qbittorrent/qBittorr ... e3b696aa95


Link 1: http://www.fosshub.com/qBittorrent.html
Link 2: http://builds.shiki.hu/qbittorrent_3.2. ... _setup.exe

[Nemo]

Thanks sledge! Love your work mate. Not to forget others work also, thanks to everyone who put their time and effort in it.

Installing and replacing my previous alpha right away.

[nico910]

Ty sledgehammer_999, i like the new "save as" display

[LoKout]

Haven't done much testing but I previously had the nightly from 20150201 installed, which had issues with missing files upon restart.  I ended up with the same situation with the nightly from 20150308, but upon restart they all checked out and started seeding.  Anecdotal for now, but I'll keep an eye on other reported issues as well to see if I notice any odd behavior.

I happen to currently have 197 transfers (194 seeding, 3 paused, 2 active) so I should be able to report on high memory/cpu utilization with libtorrent 1.x in a couple of days.

[Douman]

@sledg,

I found interesting thing. It seems latest builds make double-initialization: