According to the PR on github this is likely just a bug with the implementation that makes htop (etc) display wrong RAM usage numbers. It seems as of now as there is "no magic happening". People reported much higher actual RAM usage. The author acknowledged that it might be a bug when he posted the PR.
No comments yet.