[go-nuts] cgo memory fragmetation?

2019-10-07 Thread miha . vrhovnik
Hi guys, We are having a very weird problem, where the process memory keeps rising, but both the pprof and valgrind report no memory leaks. But the RSS just keeps rising.The C part is in external so library To be more exact, the pprof when the process becomes idle reports a few megabytes used

Re: [go-nuts] cgo memory fragmetation?

2019-10-07 Thread miha . vrhovnik
This doesn't seem to help... gc 589 @171.013s 0%: 0.012+0.69+0.17 ms clock, 0.41+0.079/2.9/1.6+5.5 ms cpu, 6->6->5 MB, 7 MB goal, 32 P scvg: 0 MB released scvg: inuse: 7, idle: 54, sys: 61, released: 54, consumed: 7 (MB) scvg: inuse: 7, idle: 54, sys: 61, released: 54, consumed: 7 (MB) scvg:

Re: [go-nuts] cgo memory fragmetation?

2019-10-07 Thread Jamil Djadala
On Mon, 7 Oct 2019 00:54:32 -0700 (PDT) miha.vrhov...@gmail.com wrote: > Hi guys, > > We are having a very weird problem, where the process memory keeps > rising, but both the pprof and valgrind report no memory leaks. But > the RSS just keeps rising.The C part is in external so library > > To

[go-nuts] Re: Clarification on unsafe conversion between string <-> []byte

2019-10-07 Thread Serhat Şevki Dinçer
Turns out it did not really need uintptr so I switched to unsafe.Pointer. Also added more tests. Thanks Francis.. On Friday, October 4, 2019 at 12:38:22 PM UTC+3, fra...@adeven.com wrote: > > Serhat, > > That implementation looks very tidy. But it still uses uintptr. So it > doesn't solve the

[go-nuts] Re: Clarification on unsafe conversion between string <-> []byte

2019-10-07 Thread francis
Thank you Serhat :) On Monday, October 7, 2019 at 10:04:05 AM UTC+2, Serhat Şevki Dinçer wrote: > > Turns out it did not really need uintptr so I switched to unsafe.Pointer. > Also added more tests. > > Thanks Francis.. > > On Friday, October 4, 2019 at 12:38:22 PM UTC+3, fra...@adeven.com

Re: [go-nuts] cgo memory fragmetation?

2019-10-07 Thread Ian Lance Taylor
On Mon, Oct 7, 2019 at 12:54 AM wrote: > > We are having a very weird problem, where the process memory keeps rising, > but both the pprof and valgrind report no memory leaks. But the RSS just > keeps rising.The C part is in external so library In the absence of other memory pressure on the

Re: [go-nuts] cgo memory fragmetation?

2019-10-07 Thread miha . vrhovnik
It's not that. The system had 4G of memory initially as it is supposed to be enough for 18 processors (They should max out at around 250M but have the typical of about 100M) and it started swapping heavily. (I then raised the limits to 16G) so things can continue to run. BR, Miha On Monday,

[go-nuts] Full Commit Hashes in go.mod

2019-10-07 Thread mankad
Hi All! I was working on a project that ingests information about sources used a Go project, and was wondering if there was a flag that could generate a go mod file with a full commit hash instead of just pseudo versions. If not, where could I post to request to make one? Let me know and I

[go-nuts] Re: trace tool showing goroutines moving between procs after LockOSThread

2019-10-07 Thread Chris Hines
I am pretty sure that a "proc" in the trace visualization output is the same as a "P" in the parlance of the Go runtime scheduler. In the scheduler an OS thread is an "M" and even when using LockOSThread the locked goroutine and thread need to be paired up with one of the scheduler's Ps in

[go-nuts] Re: Getting Gobot package fails

2019-10-07 Thread ndhrones
When changing to 'github.com/hybridgroup/gobot' what should imports path look like in go code? On Sunday, September 22, 2019 at 11:14:48 AM UTC-4, Arie van Wingerden wrote: > > When I issue this command (as instructed on Gobot site): > go get -d -u gobot.io/x/gobot/... > > I get this