Feature request: add WithEncoderMaxMemory option

[sirzooro]

It is not possible to limit how much memory Encoder may use, what causes OOM problems with long-living encoders in embedded systems. Additionally Reset function does not free all memory, it clears buffers using x.y = x.y[:0], so allocated memory is not freed. This means that after compressing some extra long message memory usage grows and stays on higher level. I have checked existing encoder options and did not find one to limit memory usage. There are WithLowerEncoderMem and WithWindowSize which should help a bit, but I am afraid that they will not be enough in all cases. Please add new option WithEncoderMaxMemory to address this issue.

[klauspost]

Not likely to be added. You will need to manage this... Read through the discussions.. Here are some recent discussions you can start with...

#1025

#1006

[sirzooro]

Thanks, I will check them.
BTW, What about different feature, deallocate memory in Reset when size of all allocated buffers is above some threshold? This would allow to clear extra memory after spike occurred.