TheFeelTrain

You saying that made me actually look into it more, I saw a bunch of kernel-related messages so my eyes glazed over it and assumed it was the same problem, that is my bad. It seems that I had actually ran out of memory. I used to see these same messages after the old issue as well so it *seemed* like the same thing but this time there are no kernels errors in front of it, just the OOM errors. May 30 23:49:12 unRAID kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/docker/1ce2e085daba11a7bb558dd82aaff85baa717288036b63f77ab269c351c810e5,task=qbittorrent-nox,pid=14902,uid=99 May 30 23:49:12 unRAID kernel: Out of memory: Killed process 14902 (qbittorrent-nox) total-vm:10117188kB, anon-rss:9015660kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:18332kB oom_score_adj:0 May 30 23:49:14 unRAID kernel: oom_reaper: reaped process 14902 (qbittorrent-nox), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB Although I've never had this problem before, I have 32GB and it generally sits around 60% usage with around 30 docker images running so I'm not sure how it happened. I didn't change anything else but the qbittorrent one. The 4.3.9-2-01 image has been running fine since that day so could it be a memory leak on the newer images? Or do I just have some other issue I need to track down? I think using the latest v1 image did reset some settings in qbittorrent so maybe it set the max memory to unlimited or something to that effect? But that's just a guess.

I tried using the latest `libtorrentv1` image and after a couple days I got the same crash I was getting with the v2 images. I'm moving back to `binhex/arch-qbittorrentvpn:4.3.9-2-01` since that has always been stable for me.