Please allow for lower memory limit and temporary analyzer disable

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?

1 Like

I’m a fan of this, we’ll discuss internally soon.

Let me know if this solution is actually working for you!

1 Like

Yes, it works. I have the setup running with the lower memory for almost a week, and I had only two unintentional capture stops. With 0.5GB limit I had one almost everyday.

Not to mention faster screen update.

1 Like