qbittorrent: "Valgrind cannot continue. Sorry."

[themusicgod1]

this is what happens, after running

# valgrind qbittorrent

...
==111653==
==111653== Valgrind's memory management: out of memory:
==111653== memcheck:allocate new SecMap's request for 16384 bytes failed.
==111653== 2,761,490,432 bytes have already been mmap-ed ANONYMOUS.
==111653== Valgrind cannot continue. Sorry.
==111653==
==111653== There are several possible reasons for this.
==111653== - You have some kind of memory limit in place. Look at the
==111653== output of 'ulimit -a'. Is there a limit on the size of
==111653== virtual memory or address space?
==111653== - You have run out of swap space.
==111653== - Valgrind has a bug. If you think this is the case or you are
==111653== not sure, please let us know and we'll try to fix it.
==111653== Please note that programs can take substantially more memory than
==111653== normal when running under Valgrind tools, eg. up to twice or
==111653== more, depending on the tool. On a 64-bit machine, Valgrind
==111653== should be able to make use of up 32GB memory. On a 32-bit
==111653== machine, Valgrind should be able to use all the memory available
==111653== to a single process, up to 4GB if that's how you have your
==111653== kernel configured. Most 32-bit Linux setups allow a maximum of
==111653== 3GB per process.
==111653==
==111653== Whatever the reason, Valgrind cannot continue. Sorry.

i've got plenty of swap (21GB) so it *shouldn't* be that.

nothing obviously limiting in ulimit:

# ulimit -a
real-time non-blocking time (microseconds, -R) unlimited
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 29990
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 95
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 29990
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

valgrind:
  Installed: 1:3.18.1-1ubuntu2
  Candidate: 1:3.18.1-1ubuntu2
  Version table:
 *** 1:3.18.1-1ubuntu2 500
        500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

qbittorrent:
  Installed: 4.4.1-2
  Candidate: 4.4.1-2
  Version table:
 *** 4.4.1-2 500
        500 http://muug.ca/mirror/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status

ubuntu: 22.04.02 jammy LTS

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: valgrind 1:3.18.1-1ubuntu2
Uname: Linux 6.0.7-gnulibre-squashfix x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 4 00:38:15 2023
InstallationDate: Installed on 2017-04-18 (2267 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: valgrind
UpgradeStatus: Upgraded to jammy on 2023-06-14 (19 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

[themusicgod1 (themusicgod1)]

looking closer at memory/swap usage in top / free
free mem drops to around ~100M then oscillates
swap does not drop at all...so swap is fine ( 19852796 kb according to free )

/proc/sys/vm/swappiness :
60

the process that is pinned at 100% CPU at the time is memcheck-amd64...

[Pjfloyd (pjfloyd)]

Try with a recent version of Valgrind. 3.18 isn't quite ancient history but it is old, and I'm not going to try to investigate anything for such an old version.