qBittorrent 4.4.0 crashed

deekerman commented

2026-02-21 23:06:53 -05:00

Owner

Originally created by @shae-o-nell on GitHub (Jan 8, 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.19043 x86_64

What is the problem?

QBt 4.4.0 crashes when I try to launch it with more than 12k torrents total and 1 - 2 k seeding.

Steps to reproduce

qBittorrent 4.4.0. Previous versions up to 4.4 rc1 work fine.
A lot of torrents (more than 12 k in my case)
Resume data storage type set to Fastresume files

Additional context

I reproduced this crash on two different PCs running Win10, qBitttorent both in standard installation and portable mode.

I've found two ways to "fix" this crash:

rolling back to 4.3.9 or 4.4 rc1, launching qBit, stopping all torrents, then updating to 4.4.0. In this case it starts ok.
Setting Resume data storage type to SQLite. In this case 4.4.0 starts like it should even with13k total, 2k seeding and 4k downloading (queued) torrents

Log(s) & preferences file(s)

Caught signal: SIGSEGV

#  0 qbittorrent.exe      0x00007ff7060c984c straceWin::getBacktrace()[ app\stacktrace_win.h : 220 ]
#  1 qbittorrent.exe      0x00007ff7060ca9cb sigAbnormalHandler(signum)[ app\main.cpp : 368 ]
#  2 qbittorrent.exe      0x00007ff706eff715 _seh_filter_exe(xcptnum, pxcptinfoptrs)[ minkernel\crts\ucrt\src\appcrt\misc\exception_filter.cpp : 215 ]
#  3 qbittorrent.exe      0x00007ff706f84ab7 `__scrt_common_main_seh'::`1'::filt$0()[ d:\agent\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl : 304 ]
#  4 qbittorrent.exe      0x00007ff706ee015c __C_specific_handler(ExceptionRecord, EstablisherFrame, ContextRecord, DispatcherContext)[ d:\agent\_work\1\s\src\vctools\crt\vcruntime\src\eh\riscchandler.cpp : 277 ]
#  5 ntdll.dll            0x00007ffa922920cf _chkstk()
#  6 ntdll.dll            0x00007ffa92241454 RtlRaiseException()
#  7 ntdll.dll            0x00007ffa92290bfe KiUserExceptionDispatcher()
#  8 qbittorrent.exe      0x00007ff706384a95 libtorrent::file_storage::file_path(index, index, save_path)[ g:\qbittorrent\libtorrent\src\file_storage.cpp : 983 ]
#  9 qbittorrent.exe      0x00007ff70611094f BitTorrent::TorrentImpl::TorrentImpl(session, nativeSession, nativeHandle, params)[ base\bittorrent\torrentimpl.cpp : 283 ]
# 10 qbittorrent.exe      0x00007ff70610143f BitTorrent::Session::createTorrent(nativeHandle)[ base\bittorrent\session.cpp : 4600 ]
# 11 qbittorrent.exe      0x00007ff706101caa BitTorrent::Session::handleAddTorrentAlert(p)[ base\bittorrent\session.cpp : 4665 ]
# 12 qbittorrent.exe      0x00007ff706101198 BitTorrent::Session::handleAlert(a, a)[ base\bittorrent\session.cpp : 4516 ]
# 13 qbittorrent.exe      0x00007ff706100f0f BitTorrent::Session::readAlerts()[ base\bittorrent\session.cpp : 4479 ]
# 14 qbittorrent.exe      0x00007ff706100550 BitTorrent::Session::startUpTorrents()[ base\bittorrent\session.cpp : 4387 ]
# 15 qbittorrent.exe      0x00007ff7060c0546 Application::exec(params, params)[ app\application.cpp : 672 ]
# 16 qbittorrent.exe      0x00007ff7060ca7a9 main(argc, argv)[ app\main.cpp : 311 ]
# 17 qbittorrent.exe      0x00007ff706eba45f WinMain()
# 18 qbittorrent.exe      0x00007ff706ec1132 __scrt_common_main_seh()[ d:\agent\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl : 288 ]
# 19 KERNEL32.DLL         0x00007ffa90407034 BaseThreadInitThunk()
# 20 ntdll.dll            0x00007ffa92242651 RtlUserThreadStart()

Originally created by @shae-o-nell on GitHub (Jan 8, 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.19043 x86_64 ### What is the problem? QBt 4.4.0 crashes when I try to launch it with more than 12k torrents total and 1 - 2 k seeding. ### Steps to reproduce 1. qBittorrent 4.4.0. Previous versions up to 4.4 rc1 work fine. 2. A lot of torrents (more than 12 k in my case) 3. Resume data storage type set to `Fastresume files` ### Additional context I reproduced this crash on two different PCs running Win10, qBitttorent both in standard installation and portable mode. I've found two ways to "fix" this crash: 1. rolling back to 4.3.9 or 4.4 rc1, launching qBit, stopping all torrents, then updating to 4.4.0. In this case it starts ok. 2. Setting Resume data storage type to `SQLite`. In this case 4.4.0 starts like it should even with13k total, 2k seeding and 4k downloading (queued) torrents ### Log(s) & preferences file(s) Caught signal: SIGSEGV ``` # 0 qbittorrent.exe 0x00007ff7060c984c straceWin::getBacktrace()[ app\stacktrace_win.h : 220 ] # 1 qbittorrent.exe 0x00007ff7060ca9cb sigAbnormalHandler(signum)[ app\main.cpp : 368 ] # 2 qbittorrent.exe 0x00007ff706eff715 _seh_filter_exe(xcptnum, pxcptinfoptrs)[ minkernel\crts\ucrt\src\appcrt\misc\exception_filter.cpp : 215 ] # 3 qbittorrent.exe 0x00007ff706f84ab7 `__scrt_common_main_seh'::`1'::filt$0()[ d:\agent\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl : 304 ] # 4 qbittorrent.exe 0x00007ff706ee015c __C_specific_handler(ExceptionRecord, EstablisherFrame, ContextRecord, DispatcherContext)[ d:\agent\_work\1\s\src\vctools\crt\vcruntime\src\eh\riscchandler.cpp : 277 ] # 5 ntdll.dll 0x00007ffa922920cf _chkstk() # 6 ntdll.dll 0x00007ffa92241454 RtlRaiseException() # 7 ntdll.dll 0x00007ffa92290bfe KiUserExceptionDispatcher() # 8 qbittorrent.exe 0x00007ff706384a95 libtorrent::file_storage::file_path(index, index, save_path)[ g:\qbittorrent\libtorrent\src\file_storage.cpp : 983 ] # 9 qbittorrent.exe 0x00007ff70611094f BitTorrent::TorrentImpl::TorrentImpl(session, nativeSession, nativeHandle, params)[ base\bittorrent\torrentimpl.cpp : 283 ] # 10 qbittorrent.exe 0x00007ff70610143f BitTorrent::Session::createTorrent(nativeHandle)[ base\bittorrent\session.cpp : 4600 ] # 11 qbittorrent.exe 0x00007ff706101caa BitTorrent::Session::handleAddTorrentAlert(p)[ base\bittorrent\session.cpp : 4665 ] # 12 qbittorrent.exe 0x00007ff706101198 BitTorrent::Session::handleAlert(a, a)[ base\bittorrent\session.cpp : 4516 ] # 13 qbittorrent.exe 0x00007ff706100f0f BitTorrent::Session::readAlerts()[ base\bittorrent\session.cpp : 4479 ] # 14 qbittorrent.exe 0x00007ff706100550 BitTorrent::Session::startUpTorrents()[ base\bittorrent\session.cpp : 4387 ] # 15 qbittorrent.exe 0x00007ff7060c0546 Application::exec(params, params)[ app\application.cpp : 672 ] # 16 qbittorrent.exe 0x00007ff7060ca7a9 main(argc, argv)[ app\main.cpp : 311 ] # 17 qbittorrent.exe 0x00007ff706eba45f WinMain() # 18 qbittorrent.exe 0x00007ff706ec1132 __scrt_common_main_seh()[ d:\agent\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl : 288 ] # 19 KERNEL32.DLL 0x00007ffa90407034 BaseThreadInitThunk() # 20 ntdll.dll 0x00007ffa92242651 RtlUserThreadStart() ```

deekerman

2026-02-21 23:06:53 -05:00

closed this issue
added the
Crash

Duplicate
labels

deekerman commented

2026-02-21 23:07:00 -05:00

Author

Owner

@norilor commented on GitHub (Jan 8, 2022):

I had the same issue which I fixed by emptying my AppData\Local\qBittorrent\BT_backup folder and progressively adding back all the files (6 by 6) until I could reproduce the crash.

Deleted the culprit (it was a single .fastresume file) and 4.4.0 is now working smoothly.

I have 140 torrents in my client, so if you've got much more I'd just roll back to 4.3.9 or switch to SQLite if you know what you're doing, because surely it is not worth the hassle.

@norilor commented on GitHub (Jan 8, 2022): I had the same issue which I fixed by emptying my _AppData\Local\qBittorrent\BT_backup_ folder and progressively adding back all the files (6 by 6) until I could reproduce the crash. Deleted the culprit (it was a single .fastresume file) and 4.4.0 is now working smoothly. I have 140 torrents in my client, so if you've got much more I'd just roll back to 4.3.9 or switch to SQLite if you know what you're doing, because surely it is not worth the hassle.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@glassez commented on GitHub (Jan 9, 2022):

Duplicate of #15955

@glassez commented on GitHub (Jan 9, 2022): Duplicate of #15955

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Jan 10, 2022):

Deleted the culprit (it was a single .fastresume file) and 4.4.0 is now working smoothly.

Do you happen to have a backup of that resume file?

I reproduced this crash on two different PCs running Win10, qBitttorent both in standard installation and portable mode.

Can you provide any reliable steps to reproduce/torrent that's causing it?

@xavier2k6 commented on GitHub (Jan 10, 2022): >Deleted the culprit (it was a single .fastresume file) and 4.4.0 is now working smoothly. Do you happen to have a backup of that resume file? >I reproduced this crash on two different PCs running Win10, qBitttorent both in standard installation and portable mode. Can you provide any reliable steps to reproduce/torrent that's causing it?

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@glassez commented on GitHub (Jan 10, 2022):

Can you provide any reliable steps to reproduce/torrent that's causing it?

It would be very appreciated 👍

@glassez commented on GitHub (Jan 10, 2022): > Can you provide any reliable steps to reproduce/torrent that's causing it? It would be very appreciated :+1:

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Jan 10, 2022):

@glassez I haven't been able to reproduce this crash with libtorrent::file_storage::file_path in stack trace at all with official builds or any of the CI builds.......from what I've seen it does seem to be only windows/official & any stack trace crash that has been provided by a user all are based on Qt5 & not Qt6.

This libtorrent::file_storage::file_path part has been encountered a good while back in #4597 (for reference)

@xavier2k6 commented on GitHub (Jan 10, 2022): @glassez I haven't been able to reproduce this crash with `libtorrent::file_storage::file_path` in stack trace at all with official builds or any of the CI builds.......from what I've seen it does seem to be only windows/official & any stack trace crash that has been provided by a user all are based on Qt5 & not `Qt6`. This `libtorrent::file_storage::file_path` part has been encountered a good while back in #4597 (for reference)

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 10, 2022):

Good evening,

it is the torrent rechecking that is causing the problem with fastresume files. I have significantly less torrent to share than the others. requesting verification on a torrent that had writing problems caused the program to crash.

since the fast files were a problem, I put it away and restart the program, something I should not do, I had no more torrent in the list when the program reopened.

I therefore take the opportunity to go under sqlitte as indicated here above. I close the program and undo the deletion of the fastresume file. I restart the program, ask for a torrent check to see that the crash problem no longer exists.

@agasthene commented on GitHub (Jan 10, 2022): Good evening, it is the torrent rechecking that is causing the problem with fastresume files. I have significantly less torrent to share than the others. requesting verification on a torrent that had writing problems caused the program to crash. since the fast files were a problem, I put it away and restart the program, something I should not do, I had no more torrent in the list when the program reopened. I therefore take the opportunity to go under sqlitte as indicated here above. I close the program and undo the deletion of the fastresume file. I restart the program, ask for a torrent check to see that the crash problem no longer exists.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 11, 2022):

@agasthene do you by any change still have the original offending fastresume? (eg in a backup). Can you share it?

@sledgehammer999 commented on GitHub (Jan 11, 2022): @agasthene do you by any change still have the original offending fastresume? (eg in a backup). Can you share it?

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

@agasthene do you by any change still have the original offending fastresume? (eg in a backup). Can you share it?
dd54cb1b492e0bc3c4c9548aa7271b23f42fd6f6.zip

@agasthene commented on GitHub (Jan 11, 2022): > @agasthene do you by any change still have the original offending fastresume? (eg in a backup). Can you share it? [dd54cb1b492e0bc3c4c9548aa7271b23f42fd6f6.zip](https://github.com/qbittorrent/qBittorrent/files/7847701/dd54cb1b492e0bc3c4c9548aa7271b23f42fd6f6.zip)

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@glassez commented on GitHub (Jan 11, 2022):

@agasthene do you by any change still have the original offending fastresume? (eg in a backup). Can you share it?
dd54cb1b492e0bc3c4c9548aa7271b23f42fd6f6.zip

And how about corresponding .torrent files from the same directory BT_backup?

@glassez commented on GitHub (Jan 11, 2022): > > @agasthene do you by any change still have the original offending fastresume? (eg in a backup). Can you share it? > > [dd54cb1b492e0bc3c4c9548aa7271b23f42fd6f6.zip](https://github.com/qbittorrent/qBittorrent/files/7847701/dd54cb1b492e0bc3c4c9548aa7271b23f42fd6f6.zip) And how about corresponding .torrent files from the same directory BT_backup?

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

676ba95976db26e8f41f4926679381034ce5fcb3.zip
fastresume and .torrent

@agasthene commented on GitHub (Jan 11, 2022): [676ba95976db26e8f41f4926679381034ce5fcb3.zip](https://github.com/qbittorrent/qBittorrent/files/7848158/676ba95976db26e8f41f4926679381034ce5fcb3.zip) fastresume and .torrent

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@glassez commented on GitHub (Jan 11, 2022):

676ba95976db26e8f41f4926679381034ce5fcb3.zip fastresume and .torrent

Does it crash if you leave only these torrents in BT_backup and start it?

@glassez commented on GitHub (Jan 11, 2022): > [676ba95976db26e8f41f4926679381034ce5fcb3.zip](https://github.com/qbittorrent/qBittorrent/files/7848158/676ba95976db26e8f41f4926679381034ce5fcb3.zip) fastresume and .torrent Does it crash if you leave only these torrents in BT_backup and start it?

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

if i delete the fastresume files leaving the fastresume file configuration, at restart the list in the software is empty.

it's easy to test.

@agasthene commented on GitHub (Jan 11, 2022): if i delete the fastresume files leaving the fastresume file configuration, at restart the list in the software is empty. it's easy to test.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

on the other hand, in sqlite adding a torrent (no matter which one) via a link makes the application crash

@agasthene commented on GitHub (Jan 11, 2022): on the other hand, in sqlite adding a torrent (no matter which one) via a link makes the application crash

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@glassez commented on GitHub (Jan 11, 2022):

fastresume file configuration

What's it about?

We are talking here about crash during qBittorrent v4.4 startup.
@norilor said that he had detected the torrent that provokes the crash (i.e. deleting the .fastresume file of this torrent from the BT_backup folder fixes the startup). We are asking if someone can provide such a "bad" torrent (corresponding .torrent and .fastresume files), which exactly leads to a crash at startup. So I assumed that you provided exactly such torrents. But they work for me without problems.

@glassez commented on GitHub (Jan 11, 2022): > fastresume file configuration What's it about? We are talking here about crash during qBittorrent v4.4 startup. @norilor said that he had detected the torrent that provokes the crash (i.e. deleting the .fastresume file of this torrent from the BT_backup folder fixes the startup). We are asking if someone can provide such a "bad" torrent (corresponding .torrent and .fastresume files), which exactly leads to a crash at startup. So I assumed that you provided exactly such torrents. But they work for me without problems.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

I think the problem is not there.

Is it the fastresume file that is the problem? Or is the problem elsewhere?

Many people say that there is a torrent verification that is done at startup and that it crashes at that moment

So I have to force a verification of a torrent, this is a problem.

The solution that was found to avoid the crash was to delete the fastresume file.

I have deleted all the fastresum files and I find myself with an empty list.

So if someone deletes a fastresume file he should find himself with one less torrent in his list.

In the end the problem is not, I think, in the fastresume file

I suggest that everyone redo an identical and detailed procedure and give his result.

Translated with www.DeepL.com/Translator (free version) (i'm speek french)

@agasthene commented on GitHub (Jan 11, 2022): I think the problem is not there. Is it the fastresume file that is the problem? Or is the problem elsewhere? Many people say that there is a torrent verification that is done at startup and that it crashes at that moment So I have to force a verification of a torrent, this is a problem. The solution that was found to avoid the crash was to delete the fastresume file. I have deleted all the fastresum files and I find myself with an empty list. So if someone deletes a fastresume file he should find himself with one less torrent in his list. In the end the problem is not, I think, in the fastresume file I suggest that everyone redo an identical and detailed procedure and give his result. Translated with www.DeepL.com/Translator (free version) (i'm speek french)

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

the test that I did not make it seems to me is to force a reverification with a torrent which did not pose problem of writing to check if the problem continued

@agasthene commented on GitHub (Jan 11, 2022): the test that I did not make it seems to me is to force a reverification with a torrent which did not pose problem of writing to check if the problem continued

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 11, 2022):

@agasthene I will try to keep it simple.
The crash report you posted indicates that the problem is during the initial loading of saved torrents.
The loading needs 2 things for each torrent. It needs the .torrent file and the .fastresume file. So one of the torrents has something weird in those 2 files that crashes qbittorrent. So we need those 2 files to test. These should belong to a torrent that causes the crash. If you send us a torrent that doesn't cause the crash then we can't help. If you fixed the problem and don't have any torrent that causes a crash then just say so.

@sledgehammer999 commented on GitHub (Jan 11, 2022): @agasthene I will try to keep it simple. The crash report you posted indicates that the problem is during the initial loading of saved torrents. The loading needs 2 things for each torrent. It needs the .torrent file and the .fastresume file. So one of the torrents has something weird in those 2 files that crashes qbittorrent. So we need those 2 files to test. These should belong to a torrent that causes the crash. If you send us a torrent that doesn't cause the crash then we can't help. If you fixed the problem and don't have any torrent that causes a crash then just say so.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

I recap, since there seems to be a mix of all contributors. I indicated that by forcing the verification of a torrent that had problems it crashed, the initial posts referred to a verification at startup that crashed the application with a number of torrent much higher

one of the torrents I posted to you had input and output problems, the check was crashing with the fastresume file.
Under sqlite the crash problem does not exist when forcing the verification

the solution that another contributor had found to solve the problem was to delete the fastresume file. however i indicated that since the number of torrent that i have in my list was smaller, that i had deleted all the fastresume file, it was deleting the torrent from the displayed list. so the one who solved the problem like that didn't really solve it since he lost a torrent

Hence my question to know if it is really the fastresume file that is the problem

Translated with www.DeepL.com/Translator (free version)

@agasthene commented on GitHub (Jan 11, 2022): I recap, since there seems to be a mix of all contributors. I indicated that by forcing the verification of a torrent that had problems it crashed, the initial posts referred to a verification at startup that crashed the application with a number of torrent much higher one of the torrents I posted to you had input and output problems, the check was crashing with the fastresume file. Under sqlite the crash problem does not exist when forcing the verification the solution that another contributor had found to solve the problem was to delete the fastresume file. however i indicated that since the number of torrent that i have in my list was smaller, that i had deleted all the fastresume file, it was deleting the torrent from the displayed list. so the one who solved the problem like that didn't really solve it since he lost a torrent Hence my question to know if it is really the fastresume file that is the problem Translated with www.DeepL.com/Translator (free version)

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

I had also announced that I had not tested the forcing of the verification with another torrent which did not pose any problem. thing made but not in the same condition of departure and I do not have problem of crash.

Concerning the torrent in question that I sent you. if I had problems of reading and writing (e/s) with these files and the fast resume option, I forced a recheck with the sqlite option. under this option it did not pose any problem.

@agasthene commented on GitHub (Jan 11, 2022): I had also announced that I had not tested the forcing of the verification with another torrent which did not pose any problem. thing made but not in the same condition of departure and I do not have problem of crash. Concerning the torrent in question that I sent you. if I had problems of reading and writing (e/s) with these files and the fast resume option, I forced a recheck with the sqlite option. under this option it did not pose any problem.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 11, 2022):

@agasthene can you post the sections from the log file that were written when you run 4.4.0 and it crashed? It might contain info that will help us diagnose the issue.
Be sure to censor stuff like torrent hashes, torrent names, IP addresses etc.
By default the log is in C:\Users\username\AppData\Local\qBittorrent\logs.

@sledgehammer999 commented on GitHub (Jan 11, 2022): @agasthene can you post the sections from the log file that were written when you run 4.4.0 and it crashed? It might contain info that will help us diagnose the issue. Be sure to censor stuff like torrent hashes, torrent names, IP addresses etc. By default the log is in `C:\Users\username\AppData\Local\qBittorrent\logs`.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@norilor commented on GitHub (Jan 11, 2022):

Deleted the culprit (it was a single .fastresume file) and 4.4.0 is now working smoothly.

Do you happen to have a backup of that resume file?

I don't, unfortunately.

And the torrents provided above work fine for me too.

@norilor commented on GitHub (Jan 11, 2022): > > Deleted the culprit (it was a single .fastresume file) and 4.4.0 is now working smoothly. > > Do you happen to have a backup of that resume file? I don't, unfortunately. And the torrents provided above work fine for me too.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

le fichier log ne répertorie pas le problème spécifique, je vous ai mis aussi les fihcier bak
the log file does not list the specific problem, I also put the bak files
Uploading qbittorrent.zip…

@agasthene commented on GitHub (Jan 11, 2022): le fichier log ne répertorie pas le problème spécifique, je vous ai mis aussi les fihcier bak the log file does not list the specific problem, I also put the bak files [Uploading qbittorrent.zip…]()

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 11, 2022):

@agasthene the upload hasn't completed. Can you post it again?

@sledgehammer999 commented on GitHub (Jan 11, 2022): @agasthene the upload hasn't completed. Can you post it again?

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 11, 2022):

qbittorrent.zip

@agasthene commented on GitHub (Jan 11, 2022): [qbittorrent.zip](https://github.com/qbittorrent/qBittorrent/files/7850009/qbittorrent.zip)

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 11, 2022):

@glassez I located these in the logs which are in french.

Alerte d'erreur fichier. Torrent : "XXXXX". Fichier : "D:\Downloads\XXXXX.iso". Motif : XXXXX partfile_read (D:\Downloads\XXXXX.iso) error: No such file or directory

which I think translates to:

File error alert. Torrent: "XXXXX". File: "D:\Downloads\XXXXX.iso". Reason: XXXXX partfile_read (D:\Downloads\XXXXX.iso) error: No such file or directory

and

Différence de tailles de fichiers pour le torrent "XXXXX". Impossible de continuer.

which translates to:

File sizes mismatch for torrent 'XXXXX'. Cannot proceed further.

The first error affects 2 torrents. The second error appears for 3 torrents (the 2 previous and one more).

@sledgehammer999 commented on GitHub (Jan 11, 2022): @glassez I located these in the logs which are in french. >Alerte d'erreur fichier. Torrent : "XXXXX". Fichier : "D:\Downloads\XXXXX.iso". Motif : XXXXX partfile_read (D:\Downloads\XXXXX.iso) error: No such file or directory which I think translates to: >File error alert. Torrent: "XXXXX". File: "D:\Downloads\XXXXX.iso". Reason: XXXXX partfile_read (D:\Downloads\XXXXX.iso) error: No such file or directory and >Différence de tailles de fichiers pour le torrent "XXXXX". Impossible de continuer. which translates to: >File sizes mismatch for torrent 'XXXXX'. Cannot proceed further. The first error affects 2 torrents. The second error appears for 3 torrents (the 2 previous and one more).

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 11, 2022):

@agasthene do you save your torrents under D:\Downloads\ and F:\Download\? Are those file paths correct?

@sledgehammer999 commented on GitHub (Jan 11, 2022): @agasthene do you save your torrents under `D:\Downloads\` and `F:\Download\`? Are those file paths correct?

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@glassez commented on GitHub (Jan 12, 2022):

Close it since there are too many duplicates.

@glassez commented on GitHub (Jan 12, 2022): Close it since there are too many duplicates.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@agasthene commented on GitHub (Jan 12, 2022):

if there are many crashes listed, they don't all have the same cause.
this topic is the most commented about this reading problem.
If there are duplicates there should be a merge
and to answer the previous question, there are 2 different directories for different torrents.

@agasthene commented on GitHub (Jan 12, 2022): if there are many crashes listed, they don't all have the same cause. this topic is the most commented about this reading problem. If there are duplicates there should be a merge and to answer the previous question, there are 2 different directories for different torrents.

deekerman commented

2026-02-21 23:07:06 -05:00

Author

Owner

@glassez commented on GitHub (Jan 12, 2022):

if there are many crashes listed, they don't all have the same cause.

You are personally discussing a problem different from the one described by the author of this topic.

@glassez commented on GitHub (Jan 12, 2022): > if there are many crashes listed, they don't all have the same cause. You are personally discussing a problem different from the one described by the author of this topic.

Rows
Columns

qBittorrent 4.4.0 crashed #12739

qBittorrent & operating system versions

What is the problem?

Steps to reproduce

Additional context

Log(s) & preferences file(s)