Closed primalmotion closed 4 years ago
I notice the following panic when mongo is not super responsive (ie I was running a huge indexing operation)
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1460412] goroutine 123 [running]: go.aporeto.io/backend/vendor/github.com/globalsign/mgo.(*Collection).writeOp(0xc00191c210, 0x30f1260, 0xc001aab660, 0xc001aab601, 0x0, 0x0, 0x0) /tmp/build/ae5c2d4a/go/src/go.aporeto.io/backend/vendor/github.com/globalsign/mgo/session.go:5366 +0x6e2 go.aporeto.io/backend/vendor/github.com/globalsign/mgo.(*Bulk).runUpdate(0xc0019d8b70, 0xc001cbcec0, 0xc0015b3340, 0xc001aab640, 0x0) /tmp/build/ae5c2d4a/go/src/go.aporeto.io/backend/vendor/github.com/globalsign/mgo/bulk.go:330 +0x97 go.aporeto.io/backend/vendor/github.com/globalsign/mgo.(*Bulk).Run(0xc0019d8b70, 0x3, 0x22, 0xc000193980) /tmp/build/ae5c2d4a/go/src/go.aporeto.io/backend/vendor/github.com/globalsign/mgo/bulk.go:297 +0x271 go.aporeto.io/backend/srv/gaga/internal/reports.(*PUPoker).handlePoke.func1()
I notice the following panic when mongo is not super responsive (ie I was running a huge indexing operation)