It's coincident. I will explain below.
Seems like we have the most likely culprit stated here.
The memory management feature should have been disabled by default. The problem is people freaked out because they suddenly see they don't have any free RAM anymore, thus made
@RMerlin enable it by default. In actuality most of the RAM used was for precious caching, making processes running faster with likely more cache hits. Having process caches evicted aggressively will lead to the opposite, cache misses and I have noticed smbd (for NAS) and transmission either crashed or killed by oom (without swap at the time though) because of this feature enabled.
With dnscrypt-proxy version 2 written in Go, I don't know the actual implementation but it seems to use a lot of virtual memory, thus having this feature enabled
likely (the coincident happens more frequently) get it to be killed more quickly by OOM.
Personally I would propose
@RMerlin disable the memory management feature and change the way webui reports mem usage to user by counting cache memory as free mem, considering cache will get evicted by the kernel as needed anyway. It's not technically correct but it'd give a more stable experience as well as make the less technical inclined people not freaking out about their RAM usage.
P.S. Not so sure, but I believe Windows counts cache as free RAM as well.