I figured it. My exec.Command's were leaving a bunch of zombie processes.
Had to do cmd.Wait() on them to exit cleanly.
On Thursday, June 1, 2017 at 9:25:51 PM UTC-7, Dmitry Mishin wrote:
>
> I have the same impression...
>
> Added a 300 msec sleep before each folder read task
I have the same impression...
Added a 300 msec sleep before each folder read task. Will see how it goes,
maybe that will let the OS recover whatever resources it's missing...
Thanks for your help!
On Thursday, June 1, 2017 at 8:09:14 PM UTC-7, Dave Cheney wrote:
>
> Imo this is not a problem wi
I was wrong about the number of folder read workers. Adding more workers
makes the error happen sooner.
On Thursday, June 1, 2017 at 6:24:48 PM UTC-7, Dmitry Mishin wrote:
>
> What I'm wondering about is the time it takes to get the error - very
>> close to 10 minutes all t
:13:53 PM UTC-7, Dmitry Mishin wrote:
>
> The system has 1GB of swap, and I just tried enabling:
>
> sysctl -w vm.overcommit_memory=1
> sysctl -w vm.swappiness=1
>
> according to
> https://stackoverflow.com/questions/35025338/cannot-allocate-memory-error,
> with no effe
everal open issues for this, search clone or
> vfork on the github.com/golang/go project, but the short version is; add
> swap.
>
> On Friday, 2 June 2017 10:41:10 UTC+10, Dmitry Mishin wrote:
>>
>> Hello all,
>>
>> Trying to fix the out of memory issue in my go