starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

qBt randomly crashes on WinSrv 22 #15386

New issue

Closed

opened 2026-02-22 02:05:01 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-22 02:05:01 -05:00

Owner

Originally created by @LordZozzy on GitHub (Jan 14, 2024).

qBittorrent & operating system versions

qBittorrent: 4.6.2 x64
OS: Windows Server 2022 (10.0.20348) 21H2 (build 20348.2227) Datacenter (virtual)
Qt: 6.4.3
Libtorrent: 2.0.9.0, 1.2.19.0

What is the problem?

If left to its own devices, qBittorrent will randomly crash, usually within 24hrs of starting it. (I know the approximation because I run a Powershell script as a scheduled task to monitor and restart the process, and report to me via e-mail)

Qbt's own log does not contain any information regarding to this, however I have found suspicious Windows Event Log entries that might suggest there's maybe a memory leak issue.

Steps to reproduce

Start qBittorrent
Go about on your business
Realize QBT crashed

Additional context

I don't know if this matters, but the OS is running in an ESXi VM, with the main storage array as a raw data mount. It has 4 CPU core and 12GB of RAM.

According to the monitoring script, the last tw crashes occured around Jan 14th 04:10 and around 8:30. The above mentioned memory leak-suspicious entries correlate with this (the entries are at 04:07 and 08:28).

Log(s) & preferences file(s)

qbittorrent.log
qbittorrent.ini
event_logs.zip

Originally created by @LordZozzy on GitHub (Jan 14, 2024). ### qBittorrent & operating system versions qBittorrent: 4.6.2 x64 OS: Windows Server 2022 (10.0.20348) 21H2 (build 20348.2227) Datacenter (virtual) Qt: 6.4.3 Libtorrent: 2.0.9.0, 1.2.19.0 ### What is the problem? If left to its own devices, qBittorrent will randomly crash, usually within 24hrs of starting it. (I know the approximation because I run a Powershell script as a scheduled task to monitor and restart the process, and report to me via e-mail) Qbt's own log does not contain any information regarding to this, however I have found suspicious Windows Event Log entries that might suggest there's maybe a memory leak issue. ### Steps to reproduce 1. Start qBittorrent 2. Go about on your business 3. Realize QBT crashed ### Additional context I don't know if this matters, but the OS is running in an ESXi VM, with the main storage array as a raw data mount. It has 4 CPU core and 12GB of RAM. According to the monitoring script, the last tw crashes occured around Jan 14th 04:10 and around 8:30. The above mentioned memory leak-suspicious entries correlate with this (the entries are at 04:07 and 08:28). ### Log(s) & preferences file(s) [qbittorrent.log](https://github.com/qbittorrent/qBittorrent/files/13931158/qbittorrent.log) [qbittorrent.ini](https://github.com/qbittorrent/qBittorrent/files/13931122/qBittorrent.ini.txt) [event_logs.zip](https://github.com/qbittorrent/qBittorrent/files/13931153/event_logs.zip)

deekerman

2026-02-22 02:05:01 -05:00

closed this issue
added the
Crash
label

deekerman commented

2026-02-22 02:05:15 -05:00

Author

Owner

@HanabishiRecca commented on GitHub (Jan 17, 2024):

Try libtorrent 1.2.19 version. The one without lt20 mark on the downloads page.

@HanabishiRecca commented on GitHub (Jan 17, 2024): Try `libtorrent` 1.2.19 version. The one **without** `lt20` mark on the downloads page.

deekerman commented

2026-02-22 02:05:15 -05:00

Author

Owner

@LordZozzy commented on GitHub (Jan 17, 2024):

Try libtorrent 1.2.9 version. The one without lt20 mark on the downloads page.

I have upgraded to 4.6.3 with libtorrent 1.2.19.0.
Now, we wait.

@LordZozzy commented on GitHub (Jan 17, 2024): > Try `libtorrent` 1.2.9 version. The one **without** `lt20` mark on the downloads page. I have upgraded to 4.6.3 with libtorrent 1.2.19.0. Now, we wait.

deekerman commented

2026-02-22 02:05:15 -05:00

Author

Owner

@LordZozzy commented on GitHub (Jan 17, 2024):

And qBt just crashed again, right on schedule - seems like the crashes occur either ~4 or ~8 hours after the process starts.
Uploading some fresh logs, and a crashdump too.
qbittorrent.log
qBittorrent.ini
qbittorrent.exe.8064.dmp

@LordZozzy commented on GitHub (Jan 17, 2024): And qBt just crashed again, right on schedule - seems like the crashes occur either ~4 or ~8 hours after the process starts. Uploading some fresh logs, and a crashdump too. [qbittorrent.log](https://github.com/qbittorrent/qBittorrent/files/13965139/qbittorrent.log) [qBittorrent.ini](https://github.com/qbittorrent/qBittorrent/files/13965141/qBittorrent.ini.txt) [qbittorrent.exe.8064.dmp](https://github.com/qbittorrent/qBittorrent/files/13965143/qbittorrent.exe.8064.dmp)

deekerman commented

2026-02-22 02:05:15 -05:00

Author

Owner

@wsy commented on GitHub (Jan 21, 2024):

I have been using qBitTorrent with libTorrent 1.x on Windows Server 2022 DataCenter edition.
I rarely shutdown my computer and I rarely restart my computer and qBitTorrent never crashes.
Even it's been running for 60 days.

Here's my configuration:
i3 7350k, 64GB DDR4, Windows is installed on 128GB SanDisk SATA SSD.
Windows Storage Space has 4 Seagate Exos HDDs and one Crucial NVMe SSD and one WD NVMe SSD and one Intel 32GB optane SSD in the storage pool.

Windows Server 2022 is running on bare metal with Hyper-V enabled.
I have about 9 Hyper-V virtual machines running all the time.
RAM load is usually 50+GB/64GB
qBitTorrent stores files on Windows Storage Space.
Today I upgraded my qBitTorrent from 4.6.2 to 4.6.3.

By the way, last month I bought and installed Intel X540-T2 PCIe card and last week I installed Nvidia GeForce GTX 650Ti.

@wsy commented on GitHub (Jan 21, 2024): I have been using qBitTorrent with libTorrent 1.x on Windows Server 2022 DataCenter edition. I rarely shutdown my computer and I rarely restart my computer and qBitTorrent never crashes. Even it's been running for 60 days. Here's my configuration: i3 7350k, 64GB DDR4, Windows is installed on 128GB SanDisk SATA SSD. Windows Storage Space has 4 Seagate Exos HDDs and one Crucial NVMe SSD and one WD NVMe SSD and one Intel 32GB optane SSD in the storage pool. Windows Server 2022 is running on bare metal with Hyper-V enabled. I have about 9 Hyper-V virtual machines running all the time. RAM load is usually 50+GB/64GB qBitTorrent stores files on Windows Storage Space. Today I upgraded my qBitTorrent from 4.6.2 to 4.6.3. By the way, last month I bought and installed Intel X540-T2 PCIe card and last week I installed Nvidia GeForce GTX 650Ti.

deekerman commented

2026-02-22 02:05:15 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 16, 2025):

This ticket has been closed.

Closure Reason: being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable.

If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.
A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Thank you for your contribution(s).

@xavier2k6 commented on GitHub (Mar 16, 2025): ### This ticket has been closed. ____ **Closure Reason: being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable.** ____ * If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. * Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. * Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. * A new issue report with relevant updated data gathered from the **latest** version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. * Thank you for your contribution(s).

deekerman referenced this issue

2026-02-22 02:30:09 -05:00

Feature Request: Add the options "Ignore seeding limits for private torrents" and "Ignore rate limits for private torrents" to the settings #15794