-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug. Version 4.1.6 is still available for download. Please take down. #10669
Comments
It works fine on Linux. |
Working fine on windows 10 as well. Dunno what @a-raccoon is going on about. |
This:
I've already suggested that v4.1.5 should be restored as the default download, a week ago: sledgehammer_999 is fully aware of the current issues, so leaving v4.1.6 up on the server doesn't make any sense at this point!: |
@THEtomaso oh well, me nor any of my friends have experienced any problems with 4.1.6 .. I've even tried to replicate some of the issues you linked myself on both mine and one of my friends computers to see if I could get a single crash and still have yet to hit one. So maybe me and him are just one of the lucky few who has a good copy of 4.1.6 or something. ¯\(ツ)/¯ |
I also find this strange after so many people reporting issues. Not sure if everyone has those issues but still, 4.1.6 shouldn't be the default version I believe. |
Perhaps more intriguing is how versions seem to be repeatedly released to the general public as official, stable releases after (what appears to be, or otherwise might as well be regardless) virtually no testing beforehand, consistently leading to very unseemly results. Even if internal testing might be debatably impractical or whatever for whatever reasons, I don't think it'd be especially difficult to go through a cycle of christening every or most releases initially as beta or RC and releasing them as stable to the public only after a bug-ironing-out period (and only then auto-notifying every user that's only on the stable branch for updates about the new, now stable version). It's not exactly a unique idea, so all things considered the current and recent state of things is somewhat baffling. |
Also, like I've pointed out on more than one occassion; I don't like the idea of including libtorrent SVN fixes in stable releases: |
Seems to be random; while one has problems the other don't, including myself. As a heavy user I didn't had any crashes or other weird things since release. I do agree with THEtomaso about the SVN fixes though. |
Anyone know how can i revert it back to the previous version without losing data? |
Simply install over, you don't lose the data. :) |
Thanks for the answer. I just did this and the installer couldn't write qbittorrent.exe and when i clicked abort installation button, it seemed to be stuck. I cancelled it, and the program was completely gone from that location lol. Actually it was gone before i cancelled it, cause the installer uninstalls it first, before installing the "new" one.. I tried to install it again in the same directory and it finished fine this time. My torrents and settings are still there, and v.4.1.5 works fine. So before installing, it's a good idea to write down the location of qBittorrent. |
qbittorrent.exe can take several minutes to close if you have a lot of activity / torrents loaded. You have to wait for the process to terminate or force close it (task manager / process explorer) before you can upgrade or downgrade in Windows. The install location isn't important to preserving your settings, since those are stored in your user directories separate and apart from the software. |
Hey, How should I comeback to 4.1.5 in Ubuntu? |
4.1.6 should be removed from default as well, as long as old fastresume exist, it would crash. |
Having the same problem on Linux with v.4.1.6... |
i got this weird issue suddenly on 4.1.6 |
Pull it! With confirmed problems, makes no sense to leave it up! Seriously damaging the reputation of qBittorrent! |
+1, i just reinstalled 4.1.5 as of now! |
It's far too late already. 6 weeks in and qBittorrent's reputation has been damaged beyond repair. A permanent nuke has been issued and most trackers now forbid clients that identify as QB from connecting to them. This repository will be converted to archive-only. It was a nice run. 😿 |
Stop spreading FUD. Nothing of the sort has happened. How about instead of spewing bullshit you start contributing to the project? Or are you too busy spamming messages like these in other threads? Making passive-agressive flame-baiting comments like these is not welcome. People are doing this out of their spare time, for the benefit of everyone. EDIT: to clarify, I am not denying that the v4.1.6 Windows release has issues. I just wanted to address the FUD comment. |
This issue has no point anymore. The only person who can do that (the maintainer) is not available but when he comes back he'll surely release 4.1.7. |
Wow. Great response. Not. |
So what BitTorrent client are people supposed to flee to? uTorrent (and BitTorrent "regular") are overrun with ads. I guess Transmission is usable, if you don't mind very limited feature set and poor DL/UL performance. |
There are good alternatives, but this is not the proper place to discuss that. |
Works superb for me. Machines and setups used:
There are about ~10 more machines I cannot bother to list (relatives, friends, coworker PCs, etc) Ps.: There is a mixed use of Server + Desktop Windows. The underlying is mix of NVMe SSD, SSD, USB, SWRAID, HWRAID. There are virtual, physical machines. The machine languages are English US, French, German. Mixed. I use SOCKS5, VPN, normal connection. Somewhere it's open, somewhere it's closed port setup. And nothing. Not. A. Crash. Some of these have had qBittorrent installed for 5-10+ versions, ie.: they've been upgraded. Some are fresh deployments. |
Bully for you, but small comfort for many others for whom it does not work. |
I know "works for me" is not especially helpful. But, it's a version that works better for me, than 4.1.5 did. (4.1.5 had this 'un-closable' problem at me.) So honestly, not sure which would be a better choice... |
If I had to guess, the crashes are circumstantial to a user state. It crashes on me, and I have 431 torrents loaded, 80% of them complete and seeding. When QB crashes, it does a recheck on all the incompleted torrents. There were a lot of changes made to rechecking / moving functions. I'll bet my sweet ass the crash loop is a file access violation. Sometimes it crashes immediately, and sometimes it crashes 3 minutes later, and then it'll crash immediately ten times in a row. |
@a-raccoon |
@Seeker2 |
qBittorrent 4.1.6 is a flawed release and should be recalled and removed from the website. Mention that it is a lemon should be appended to the Github Releases notes.
Thousands of people are downloading 4.1.6 and thousands of people are losing their minds, every hour.
The text was updated successfully, but these errors were encountered: