A similar issue has been reported to the upstream bug tracker ( https://github.com/qbittorrent/qBittorrent/issues/4379) for the same qbittorrent version (3.3.1), though for another OS.
It appears to be fixed upstream ( https://github.com/qbittorrent/qBittorrent/pull/4438) in 3.3.2. I believe the bug can be closed now. Regards BZ
