Thanks for the config.json suggestion. It worked! I have set it to 20M and the program reports 23M during capture, which is alright.
I don’t need a precise and bug-free memory limit. I just need a limit lower than it is now. In the same “suboptimal” implementation, as it is now. It would work fine for me, and I suppose it’s matter of a single change of a constant in the source code. So why not introduce it?