QbitTorrent keeps crashing/hanging

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | cat /boot/dietpi/.version
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • Kernel version | uname --all
  • Architecture | dpkg --print-architecture
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
  • Power supply used | (EG: 5V 1A RAVpower)
  • SD card used | (EG: SanDisk ultra)

Additional Information (if applicable)

  • Software title | (EG: Nextcloud)
  • Was the software title installed freshly or updated/migrated?
  • Can this issue be replicated on a fresh installation of DietPi?
    ← If you sent a ā€œdietpi-bugreportā€, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

Just running qbittorrent-nox after a little while just hangs my PI

  1. …

Expected behaviour

Should keep running

  • …

Actual behaviour

Crashes or hangs the PI

  • …

Extra details

Logs do not show anything, the amount of time between reset and crash is pretty much random.
DietPI version 5.2.2
QBitTorrent version 5.1.0 64 bit
Anyone else having similar issues?

  • …
root@DietPi:~# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=10
G_DIETPI_VERSION_SUB=5
G_DIETPI_VERSION_RC=2
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
root@DietPi:~# echo $G_DISTRO_NAME $G_RASPBIAN
trixie 0
root@DietPi:~# uname --all
Linux DietPi 6.18.34+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.18.34-1+rpt1 (2026-06-09) aarch64 GNU/Linux
root@DietPi:~# dpkg --print-architecture
arm64
Power Supply: 100w
SD Card Used: USB SSD Drive.

Which RPi model is it? Quick guess would be exhausted memory or low voltage during preak usage, e.g. when download and a flush from buffer to disk comes together or so. But it is difficult to know without logs. You do not have a screen attached to catch kernel errors at, do you?

Else enable permanent system logs:

dietpi-software uninstall 103
sudo mkdir /var/log/journal
sudo systemctl stop dietpi-ramlog
sudo umount /var/log && sudo /boot/dietpi/func/dietpi-ramlog 0
sudo reboot

Pi 3 with 1GB ram. I created a 1.5 GB swap space.

I do have a screen attached, but nothing shows up on it. I have the logs going to a non-volatile disk space. I have looked in the logs, everything is pretty much normal tasks (torrents completing). The the start up tasks start listing off in the log. No other error messages in the logs.

I ran what you suggested. Will post the logs here as soon as something gets written.

Relevant would be the kernel logs, i.e. the systemd journal, or rsyslog to fetch and store them in plain text log files.

But if the HDMI screen is not showing anything, then the system logs most likely won’t either, as systemd feeds both from the kernel ring buffer.

You could monitor things like RAM usage and CPU temperature on a dedicated SSH session or so. Also check for kernel errors earlier, like when a download started, so some disk I/O happened already:

dmesg -l 0,1,2,3
vcgemcmd get_throttled

The second show whether there was some undervoltage or frquency cap during the session, with 0x0 meaning everything is fine: https://www.raspberrypi.com/documentation/computers/os.html#get_throttled

EDIT: What boot media are you using, and what drive is qBittorrent downloading to? Maybe the shared 1.2A USB power limit causes issues, if you are using a larger (than a stick/thumb) USB drive.

root@DietPi:~# dmesg -l 0,1,2,3
vcgemcmd get_throttled
[   14.966390] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   14.968545] Bluetooth: hci0: BCM: 'brcm/BCM4345C0.raspberrypi,3-model-b-plus.hcd'
[   14.970525] Bluetooth: hci0: BCM: 'brcm/BCM4345C0.hcd'
[   14.973356] Bluetooth: hci0: BCM: 'brcm/BCM.raspberrypi,3-model-b-plus.hcd'
[   14.975558] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'
-bash: vcgemcmd: command not found

root@DietPi:~# vcgencmd get_throttled
throttled=0x0

Greg

I run the same version on a RPi 4 with 4GB of memory and do not experience this issue.

It’s a typo, the correct command is

vcgencmd get_throttled

Right thanks, a typo my end. The missing Bluetooth firmware blob is interesting (if firmware-brcm80211 is installed, which is from RPi Ltd’s own APT repository), but unrelated.

Could be a memory issue. I have slowly increased the swap size, and the crashing is less frequent. Did confirm the PI has 1GB of memory, so out of memory would make sense.