Memory management is enabled (default setting).
I still can't get my head around why for the both of you it keeps crashing/quitting after a while... Quite frustrating, I imagine.
I installed the latest 384 alpha last weekend, did a clean install, went through QiS, enabled SSH, installed amtm, created a 512Mb swapfile, installed SkyNet, Ab-Solution, Entware, pixelserv, htop, openssh-sftp-server and ran the dnscrypt-proxy installer (including the install of haveged). It just works, hasn't crashed on me a single time since I jumped on the dnscrypt v2 train. The rest of my router settings is all still at the default settings, as QoS unfortunately still doesn't work for me on the latest alpha. Oh, and I've set fixed wifi channels for both bands, which is totally unrelated too.
Those are the only things I changed/added to a clean install. And it works like a charm, beta after beta. How about deleting the /jffs/dnscrypt folder, going through the startup scripts manually removing anything related, check dnsmasq.conf.add etcetera to remove every trace of manual attempts to fix it and install it using bigeyes0x0 installer? Or even better, do a factory reset, configure your connection, install the minimum of required scripts and run
@bigeyes0x0 installer. I can't explain the issues you're experiencing (which frustrates me somehow), but I haven't seen other reports of crashes so far, as far as I'm aware, so I can't get rid of the feeling that something's wrong with your setup/memory management/swap... you name it...
If I could blame it on the beta, I would, but I just can't and I don't see other reports (or I must have missed them), but these betas are so stable, bugfixes are minimal, it's mostly added functionality with each release.
I sincerely hope you'll figure it out. Very curious to hear if a fresh install (if you're willing to do so) will solve your issues.