mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Constantly crashes after upgrading to 4.4.0 #12842
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#12842
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Symbai on GitHub (Jan 15, 2022).
qBittorrent & operating system versions
qBittorrent version: v4.4.0 (64-bit)
Libtorrent version: 2.0.5.0
Qt version: 5.15.2
Boost version: 1.78.0
OpenSSL version: 1.1.1m
zlib version: 1.2.11
OS version: Windows 10 Version 2009 10.0.22489 x86_64
What is the problem?
I was on 4.2.5 and it was stable and working. Now after I've upgraded to 4.4.0 its the second crash within 5 hours. Not to mention all the duplicated torrents appearing in my list after this upgrade. The crash below happened after I selected a torrent + its duplicated and removed them. Only one torrent has been removed, the duplicate was still in list. 2 seconds later the crash.
Caught signal: SIGABRT
Steps to reproduce
No response
Additional context
No response
Log(s) & preferences file(s)
No response
@xavier2k6 commented on GitHub (Jan 16, 2022):
seems to be a duplicate of #13911 & #14964.
@Symbai Can you provide log?
CC @glassez
@glassez commented on GitHub (Jan 16, 2022):
👍
Also screenshot with duplicated torrents will be very appreciated.
@glassez commented on GitHub (Jan 16, 2022):
@Symbai
But the contents of your BT_backup folder would help the most.
@Symbai commented on GitHub (Jan 16, 2022):
Log shows tons of:



Couldn't enqueue move of "Bla" from "Z:\123\" to "Z:\123". Both paths point to the same location.Screenshot (Filenames under black area are 100% identical):
However if I click on the
greenone, theContentarea is empty. And underGeneraltotal size is empty.vs
In
BT_backupfolder there is only one.fastresumeand one.torrentfile with this torrent info v1 hash. Unfortunately I cannot share these files but if there is anything you are interested in these files let me know and I will tell you.Restarting qbittorrent doesn't solve the duplicated torrent issues. Not all torrents are duplicated only some of them.
@glassez commented on GitHub (Jan 17, 2022):
@Symbai
Could you compare the number of
.fastresumefiles with the number of torrents in the application?These are safe (just a noise).
Interesting are those that are about "torrent restored". And some errors of course.
Okay, if you can't share the torrents, that's up to you. Could you then agree to test it yourself by running the test builds that I will offer you?
@Symbai commented on GitHub (Jan 17, 2022):
Number of .fastresume matches the number of torrents in the application. Except of two duplicates (+2 fake torrents, the green ones from the screenshot). There are no errors in the log, but log file contains more then 700 entries. Would be nice if we could filter by log type (to filter out all the unimportant entries).
Yes I can run a test build.
@glassez commented on GitHub (Jan 17, 2022):
So you have N .fastresume files and N+2 torrents in app?
@Symbai commented on GitHub (Jan 17, 2022):
Yes and for these the log only have just like most of the others:
@glassez commented on GitHub (Jan 17, 2022):
And you have two exactly the same messages for each of the duplicate torrents, right?
@Symbai commented on GitHub (Jan 17, 2022):
I have it 2 times, for 4 torrents (including duplicates). I've deleted the .fastresume and .torrent files. Then I've removed the black torrents. The green torrent immediately became black. I've deleted them as well but then qbittorrent crashed again, same error as in first post. Now when I restart qbittorrent there are no such files anymore, even if I restore .fastresume and .torrent files no duplicated torrents anymore.
@Symbai commented on GitHub (Jan 22, 2022):
Well, after a restart of qBittorrent I now have duplicated torrents again.

Also why does it still have "waiting info" label? For which info are you waiting?
@glassez commented on GitHub (Jan 23, 2022):
Is this torrent hybrid?
@Symbai commented on GitHub (Jan 23, 2022):
How can I check this? Both torrents have a v1 and v2 hash. But in
BT_backupI only find files for the v1 hash.@glassez commented on GitHub (Jan 23, 2022):
So it's hybrid torrent.
v2 hash used in reduced form as torrent id (truncated to the length of v1 hash) so you should try to search for such a torrent id.
.fastresumewith this v2 torrent if most likely should exist.@Symbai commented on GitHub (Jan 23, 2022):
Yes only a .fastresume for v2 exist.
@glassez commented on GitHub (Jan 23, 2022):
Well, then you are affected by the same bug that causes crash like #15955 under some different circumstances. The creation of a fix for this bug is already being done.
You can remove
v1.fastresumeand renamev1.torrenttov2.torrentto fix it locally.