every clib4 binary (even simply one) leak memory on the run/exit for about 1-1.5mb for each run.

[kas1e]

Topic says it all, running any clib4 based app compiled with latest beta10 cause leaking of 1-1.5mb of memory on each run. 10 runs - 15 mb, 100 runs and you have 150 mb go away. Can be reproduced even with simply "hello world" test case.

[3246251196]

@kas1e
@walkero-gr
@afxgroup
Are we able to post a simple example on this ticket?

[kas1e]

As i say any example. Simple hello world with single printf is enough

[3246251196]

okay.

[afxgroup]

We have to replace all AllocVecTags/FreeVec that are not in the constructors with malloc/free when possible

[3246251196]

What is the best tool / what tool are you using to prove the leak?

[raziel-]

cmake 😀

[3246251196]

Using a simple hello world is easiest since that program is simple. I mean, how are you proving that the bytes consumed versus the bytes released are different? What tool are you using?