-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
v4.4 has crashed due to hybrid torrents added by previous release #15955
Comments
By the way, the logs talk about the file "d:\agent_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl :" but there is no such file. |
@Informartiste |
@mzso You mean search on the Internet for torrent from inside qBittorrent ? No, never. |
This one #15886 seems very similar to mine What is strange is qBittorrent seems to work, I can see the upload/download speed evolving, but I cant use it while the windows with the crash alert is still opened. And qBittorrent closes itself when I close the alert windows. |
Maybe I have a clue ... In #15886 they talk about Category. |
I installed qBittorrent 4.3.9, it runs without crashing ... |
@Informartiste commented on 2022. jan. 7. 15:53 CET:
Probably the because they designed the crash capture feature that way. Which is unfortunate, because otherwise QB would be usable, at least to shut down normally. |
Could you suggest a code that would determine whether it can continue to work in this or that crash case? This is usually not possible. |
@glassez commented on 2022. jan. 9. 10:38 CET:
Well I'm guessing that allowing to start a normal shutdown process couldn't hurt. At worst it fails, and we're no worse off. |
For the users experiencing crashes I have 2 questions:
|
|
1. Do you use "categories" in your torrents?
* Yes, and as I said, I think it is related to Categories. Because, if I remember well:
* I was unable to set categories as in the previous version, by right-clicking some torrents
* Maybe I created an already existing categories because I was unable to see my existing ones.
* qBittorrent crashed during the next startup after I used categories.
2. Do you experience crashes with the Qt6 version too? (needs Windows 10+)
* I didn’t tried
De : sledgehammer999 ***@***.***
Envoyé : lundi 10 janvier 2022 15:17
À : qbittorrent/qBittorrent ***@***.***>
Cc : Informartiste ***@***.***>; Mention ***@***.***>
Objet : Re: [qbittorrent/qBittorrent] qBittorrent has crashed (Issue #15955)
For the users experiencing crashes I have 2 questions:
1. Do you use "categories" in your torrents?
2. Do you experience crashes with the Qt6 version too? (needs Windows 10+)
—
Reply to this email directly, view it on GitHub<#15955 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC7R5EDEI5JKY4L2EBEMYDLUVLS55ANCNFSM5LOVR32A>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Run 4.4.0 again and let it crash. Now look at the log file. By default in |
Remeber that the newest entries are the end of the file. |
This comment has been minimized.
This comment has been minimized.
@TagerW @GoldenGuy respond with details based on #15955 (comment) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
#15977 (comment) |
It doesn't look like it could be related to Categories, because Categories don't affect the paths of files in the torrent, but only the "save path" of the torrent. aux::file_entry const& fe = m_files[index]; But if passed index is wrong it should have crashed on the previous line, no? Here: TORRENT_ASSERT_PRECOND(index >= file_index_t(0) && index < end_file()); |
I am not sure what "fixed" my crash. I closed out 4.4.0 and restarted it. And now it acts like it never crashed. Not getting the error anymore. |
I got the exact same error as OP, and I think what caused it was related to switching between SQLite and Fastresume files. After windows decided to restart my computer in the middle of the night, I woke up to a crashed qBittorrent, and I know for a FACT that I switched back to Fastresume files after using SQLite database for several weeks, because qBittorrent had begun taking forever to shut down. So yeah, it does look like fastresume files are the culprit somehow. Thanks for an otherwise great bittorrent experience 👍 |
I did Force Recheck a torrent that was in Errored. After it cleared that out, I think that is what made it work fine. Not sure what exactly. But closed the crash window, which closed 4.4.0, and then restarted and the error was gone. (Even though it still worked behind the crash screen. I could not click on anything behind the crash screen. Still was downloading files.) |
@RedSnt |
I had disk space issues and left about 10GB available (I was literally on fumes before cleaning up the main drive QB was using) and it didn't cure right away but after a few restarts it appeared to resolve itself. I just wish QB would advise this without crashing sans explanation, but the end result is it's back to functioning so all's well that ends well. |
Like my 4.4.0. It started crashing for some reason. Then the next day, after attempting to see if it would work, it started up just like normal. And has been not crashing since. I did notice that even though I could only close the crash message, that would close QB as well, it was working in the background as before. I could not do anything but close the crash message and program. See what the next version states it fixed, added, etc. |
Still experiencing the same startup crash in 4.4.1 qBittorrent version: v4.4.1 (64-bit) Caught signal: SIGSEGV
|
Hmm... The problem may be something else, but similar... |
I'd like to try to help, but not quite sure how to find the "info hash". Opening .fastresume in notepad I see a combination of readable stuff and garbage characters. Can I safely clear out the .fastresume files and see if that fixes the issue without losing the torrents? |
If I add some "guard" logic to the code, will you be able to test it using the build from GitHub? |
Yeah, I can do that. |
Ok, will do it in a few days. |
Alright just let me know when it's ready. I did find two torrent files where the status is "Missing Files". Force recheck or resuming them doesn't help fix them. The .fastresume files for them have an "info-hash20" key where the value seems to just be random characters including some unprintable ones. Not sure if that's what you might have been alluding to before. |
For what it's worth this was finally fixed for me in 4.4.2 |
Same for me. Everything is fine again with 4.4.2. Thanks |
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.19044 x86_64
What is the problem?
Caught signal: SIGSEGV
Steps to reproduce
It happens each time i start qBittorent
Additional context
I installed qbittorent 4.4.0 today and since it crashes when i launch it.
I got the main qbittorent screen which seems Ok and an alert saying "qBittorrent has crashed
Please file a bug report at http://bugs.qbittorrent.org and provide the following information: ..."
When I close the alert, the main qbittorent closes itself too
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: