Hey, Vlad,
it's not that. we have a similar or rather the exactly the same problem...
where the OS doesn't claim the memory back.. this is also annoying to the
point we had to disable memory under pressure notifications for that
specific host.
Also valgrind doesn't report any leaks... simulatin
If it helps any, I do not see this in Windows 10. After 5,000 iterations
the "low memory" mark, as reported by windows, is still just 1,101MB.
On Monday, August 24, 2020 at 5:05:00 AM UTC-4 vlad...@varank.in wrote:
> Hey,
>
> I haven't looked deep but I recall there had been a note about runtim
Hey,
I haven't looked deep but I recall there had been a note about runtime
change in Go 1.13's https://golang.org/doc/go1.13#runtime That is
> The runtime is now more aggressive at returning memory to the operating
system to make it available to co-tenant applications [..] However, on many
OS
