Open LordZozzy opened 10 months ago
Try libtorrent
1.2.19 version. The one without lt20
mark on the downloads page.
Try
libtorrent
1.2.9 version. The one withoutlt20
mark on the downloads page.
I have upgraded to 4.6.3 with libtorrent 1.2.19.0. Now, we wait.
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
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.
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
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