Hi, thanks to everyone for the suggestions,
It seems that there is in fact not a memory leak (still not totally sure),
but for some reason, the go runtime keeps allocating memory event when is
not needed, I think the problem is in the interaction from the memory model
of the go runtime with a L
Are you using CGo or libraries that use CGo? If so, you probably have an
off-heap, i.e malloc() leak
> On Feb 11, 2021, at 11:11 AM, Tom Mitchell wrote:
>
>
>
>> On Thu, Feb 11, 2021 at 3:40 AM Uli Kunitz wrote:
>> You are writing: The device crashes with out of memory. What does crash? T
On Thu, Feb 11, 2021 at 3:40 AM Uli Kunitz wrote:
> You are writing: The device crashes with out of memory. What does crash?
> The Go program, another program or the kernel? Can you share the error
> message? Can you share the log file for one day of GODEBUG=gctrace=1?
>
> In bash do:
>
> $ expor
