Re: [go-nuts] Re: Unable to find small memory leak

2021-02-21 Thread Miles Hex
e 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: >> >> $ export GODEBUG=gctrace=1 >> $

[go-nuts] Re: Unable to find small memory leak

2021-02-11 Thread Miles Hex
le and start the program that calls your program. You > might keep your heap size a little bit smaller by setting GOGC to a smaller > value than 100. Here is a helpful article: > https://dave.cheney.net/tag/godebug > > On Tuesday, February 9, 2021 at 10:43:42 PM UTC+1 Miles Hex

[go-nuts] Re: Unable to find small memory leak

2021-02-09 Thread Miles Hex
ut with sort | uniq -c. >> >> On Tuesday, February 9, 2021 at 8:05:23 PM UTC+1 Miles Hex wrote: >> >>> >>> Hi, >>> >>> I'm using golang (1.15.6) to write a daemon that handle system >>> task(network, time, updates, etc..) in embedded d

[go-nuts] Unable to find small memory leak

2021-02-09 Thread Miles Hex
Hi, I'm using golang (1.15.6) to write a daemon that handle system task(network, time, updates, etc..) in embedded device (an onion omega 2+), and i'm encountering a small memory leak that i'm unable to identify and fix. The device is using linux 4.14.171, the architecture is mips. At first