Major Description
I see this panic due to a segmentation fault occasionally while I'm testing gocb with FTS (via cbgt) ..
panic: runtime error: invalid memory address or nil pointer dereference
|
[signal SIGSEGV: segmentation violation code=0x1 addr=0x70 pc=0x159be13] |
|
|
goroutine 1796 [running]: |
gopkg.in/couchbase/gocbcore%2ev7.(*Agent).StatsEx.func2(0x0, 0xc001e2c000, 0x1d3b8e0, 0x2604b00) |
▸ /Users/abhinavdangeti/Documents/couchbase/godeps/src/gopkg.in/couchbase/gocbcore.v7/agentops_crud.go:977 +0x53 |
gopkg.in/couchbase/gocbcore%2ev7.(*memdQRequest).tryCallback(0xc001e2c000, 0x0, 0x1d3b8e0, 0x2604b00, 0xc000179ef8) |
▸ /Users/abhinavdangeti/Documents/couchbase/godeps/src/gopkg.in/couchbase/gocbcore.v7/memdqpackets.go:78 +0x70 |
gopkg.in/couchbase/gocbcore%2ev7.(*memdClient).run.func2.1(0xc001e2c000) |
▸ /Users/abhinavdangeti/Documents/couchbase/godeps/src/gopkg.in/couchbase/gocbcore.v7/memdclient.go:376 +0x80 |
gopkg.in/couchbase/gocbcore%2ev7.(*memdOpMap).Drain(0xc00016e050, 0xc000179fa0) |
▸ /Users/abhinavdangeti/Documents/couchbase/godeps/src/gopkg.in/couchbase/gocbcore.v7/memdopmap.go:129 +0x3e |
gopkg.in/couchbase/gocbcore%2ev7.(*memdClient).run.func2(0xc00016e000, 0xc00028a480, 0xc00028a540, 0xc00028a5a0) |
▸ /Users/abhinavdangeti/Documents/couchbase/godeps/src/gopkg.in/couchbase/gocbcore.v7/memdclient.go:371 +0x60d |
created by gopkg.in/couchbase/gocbcore%2ev7.(*memdClient).run
|
▸ /Users/abhinavdangeti/Documents/couchbase/godeps/src/gopkg.in/couchbase/gocbcore.v7/memdclient.go:279 +0x105 |
It seems like it's possible that memcached response at this point can be nil ?
https://github.com/couchbase/gocbcore/blob/v7/agentops_crud.go#L977