On Fri, Mar 6, 2020 at 5:21 PM Christophe Meessen <
christophe.mees...@gmail.com> wrote:
>
>
However, it never gets back to the low level it had initially. Initial
> lowest Alloc is 146520. It then grows steadily up to 163040. Then suddenly
> drops to 156896, and grows slowly again to 163520.
On Fri, Mar 6, 2020 at 4:55 PM Christophe Meessen <
christophe.mees...@gmail.com> wrote:
> It would have been convenient for detecting memory leaks to be able to
compare memory Alloc before and after the checked task and a really
complete GC.
That's not feasible. There are _always_ other
While letting the program run for a few hours I see that after some time
the memory usage vary in saw teeth. Some of the garbage is reclaimed after
800 calls to GC().
However, it never gets back to the low level it had initially. Initial
lowest Alloc is 146520. It then grows steadily up to
evelopment (and most can be used in production with some caveats).-Original Message-
From: Christophe Meessen
Sent: Mar 6, 2020 9:55 AM
To: golang-nuts
Subject: [go-nuts] Re: Memory leak or GC feature ?
The documentation of the GC() function states:"GC runs a garbage collection and blocks t
The documentation of the GC() function states:
"GC runs a garbage collection and blocks the caller until the garbage
collection is complete. It may also block the entire program."
Based on the documentation, I assumed that a garbage collection would be
really complete by calling GC. By
This is normal behaviour and not a leak.
Nothing is leaking in your code (and it is generally
hard to leak RAM). The allocations will be reclaimed.
V.
On Friday, 6 March 2020 14:11:37 UTC+1, Christophe Meessen wrote:
>
> I wanted to check my program for go routine and memory leaks. In doing so
