Code crushes at the end, due to bad alloc (attempts to allocate a huge amount of memory).

[nbooster]

Hello,

it seems that this lib uses a lot of memory,
which causes my app to crash.

I am bench-marking a piece of code (function call) ~23M times,
and the memory usage goes beyond 4.3GB,
with correct output (each call to CTRACK is ~18 nanos overhead),
but when I attempt to do the same more than 30M times,
the memory explodes (more than 6.4 GB),
which causes the app to crash.

Is there a limit on the amount of calls CTRACK can be called inside an app,
or is it a bug of the lib ?

Thanks in advance.